[Clipart] Roadmap on wiki vs Blueprints
jon at rejon.org
Sun Apr 11 14:23:31 PDT 2010
I'm only saying move over the tasks from the big roadmap to the blueprints,
then map out blueprints and bugs to releases.
So the one we are about to release is 2.1.
Then, we can think big on the wiki about where we are going, and then
contain the blueprints (new features/ideas) and the bugs to the launchpad,
and think bigger.
Yes, lets do it now. I've already started it. Power to the committer.
As for the rest of the wiki, it would be great to move old things like
requests and so forth to our site sooner rather than later. Wiki is a great
place for longer term discussions and a collective memory, but our new
system Aiki is really great now for allowing more access and functionality.
And, regardless, this whole process is always a moving target. As for
project management, it seems that launchpad is winning these days, and then
we can use the big roadmap to think big.
I'll keep trying to push us towards releases at the beginning of each month.
Successful completion of the releases though is up to all of us helping out.
On Sun, Apr 11, 2010 at 4:05 PM, chovynz <chovynz at gmail.com> wrote:
> How about days? ;)
> I think the wiki is a good place, it's just that there is lots of info that
> is old. (Even on LP there is old info - some of the bugs don't even apply
> to this current version of BETA.) With a good cleanup the wiki can become
> useful again. (And an Mediawiki update from 1.6.8 to 1.15+, Jon ... Ok I'll
> get off that broken record!) The Blueprints in LP are relatively clean in
> comparison to what is available on the wiki and the LP blueprints are in an
> easy to find place.
> The wiki IS ... well... it's a wiki! everyone I know uses a wiki. But
> OCAL's wiki is a scary information bloated place, which hasn't been kept
> updated, and is discouraging for librarians to keep updating. Perhaps some
> archiving and updating would be a good thing? It depends how much you want
> to do and where you want to go with it Jon. Some leadership in that area
> would be a good thing in my humble opinion.
> The Roadmap is a different thing to Blueprints I thought. Can you describe
> your thoughts on the two? As far as I understand Roadmap is what is actually
> going to happen i.e. a TODO list for those involved to see what is on the
> table currently, whereas as Blueprint is a suggestion for TODO at an
> ethereal date sometime in teh distant future. Am I on the right track or do
> I need a direction shift?
> Basically, how do you want us to use the tools we have?
> What is your vision for the Roadmap?
> Where do you want to go with OCAL?
> etcetc on big questions.
> On 12/04/2010 8:47 a.m., Jon Phillips wrote:
> Ok, I'm game for trying/using blueprints...if no one says anything in next
> couple of hours, lets start moving...
> Maybe I was the only one using the wiki anyway ;)
> On Sun, Apr 11, 2010 at 1:16 PM, chovynz <chovynz at gmail.com> wrote:
>> I prefer Launchpad. I think the wiki is not a good place for
>> bugtracking/blueprint stuff.
>> Wiki is more for historic/discussion/FAQ/, I feel.
>> However, I won't do anything on that until I hear a consensus. So, sorry.
>> No. Won't do it today. ;)
>> On 12/04/2010 8:11 a.m., Jon Phillips wrote:
>>> Heya, we must decide. Are we going to use the launchpad blueprints or the
>>> current OpenClipArt wiki?
>>> It seems that before we go over to 2.1, we should move completely to one
>>> I would like to try the blueprints solution. I think we can get more
>>> people helping this way now that we put our bugs up on launchpad. could
>>> someone help move over our roadmap to the blueprints? Chovynz? Could we get
>>> this done asap today so we can launch in the morning?
http://rejon.status.net + skype: kidproto
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clipart