[Clipart] Roadmap on wiki vs Blueprints
jon at rejon.org
Wed Apr 28 11:37:08 PDT 2010
On Tue, Apr 27, 2010 at 12:50 PM, chovynz <chovynz at gmail.com> wrote:
> 1.) What is involved in a release? I've never known, and haven't been able
> to figure it out. Would you teach us what's involved in as much detail as
> possible without getting too technical?
Yes, mostly this has just rested in the hands of me making decisions
and pushing forward on the release. I like monthly releases to push us
to the level of doing something. I usually look at the roadmap and see
what we can get done, and right now, bassel and I just pushed on these
things, then bradphillips writes up a pressrelease and announcement,
and I've been deciding the final time to launch.
This isn't hard rules, just mostly had to do with making decisions,
experience and trying to move quick to get our community healthy once
The main reason brad has been helping is because he works for me and
bassel is my best friend so we work on things a lot together :)
> Secondary thought.
> 2.) You've been using Wiki Roadmap for awhile now. Why not try something new
> (i.e. Blueprints) and see how it goes and if it can fit into the goals and
> direction of OCAL? Can we mold it and shape it into what OCAL needs? Can we
> break it and fix it? Does it give enough info to make the direction
> available? if not, how can we re-make it into wehat we need? What do we
This is a good suggestion. Is this something you'd like to lead?
The other thing we need towards the next release is to move the old
bugs from bugzilla that are relevant, to our new launchpad-based
tracker. Then, have freedesktop.org close out our tracker there. The
other option is to just close our old tracker. Thoughts?
> I would suggest you use roadmap as a "This is what we have chosen to do,"
> and the blueprints as "This is what we can choose from," and a "Your idea
> goes here!"
Good. I like it.
> I know many people do not use the wiki roadmap. Only a certain few seem to
> (Jon, Johnny, Papapishu, Bassel, Me, a few others), and it [seems to be]
> also semi-disconnected from the OCAL community at large. How many people
> read it? I couldn't tell you. But by checking the history, I can tell you
> that not many people edit it.
> (Perhaps they feel they do not have the authority to change the roadmap
> since you (Jon, Brad, Bassel, Michi?) are the "leadership" and "direction
> team". This might be a mindset that needs looking into, to change. How will
> you (Jon/team) get feedback on this type of thing? How much help does OCAL
> need? What specifically does OCAL need help with? Can you make some job
> descriptions for people who want to get into helping out? [More vebose than
> "we need PHP Scripters!!"] What are some tasks that newbies can do? How will
> you reach them? etcetc. )
Agree. This is important...what we need most are coders to help on the
site and Aiki.
> I do know that LP is being used more than the wiki by "regular users" e.g.
> more people are reporting bugs on LP, more people are making blueprints,
> more people seem to get involved WITH the LP facility.
> I don't know! It just makes sense to at least try the [LP integrated]
> Blueprints for 6 months or more and see if it fits your/OCAL/our style and
> 3.) How is Aiki linked on the wiki? How manual is the wiki? Can page
> addendums be added to the wiki via Authorised Automatic Wiki Bot reading
> your feeds? (thinking of the Release 20.etc pages that you do...) If so,
> what other jobs could be automatic-ised using the Authorised Automatic Wiki
Yah, basically, we need more people to help out before these things
become an issue IMO.
http://rejon.status.net + skype: kidproto
More information about the clipart