<div dir="ltr">I'm only saying move over the tasks from the big roadmap to the blueprints, then map out blueprints and bugs to releases.<div><br>So the one we are about to release is 2.1.</div><div><br></div><div>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.</div>
<div><br></div><div>Yes, lets do it now. I've already started it. Power to the committer.</div><div><br></div><div>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.</div>
<div><br>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.</div><div><br></div><div>
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.</div><div><br></div><div>Cheers!</div><div><br></div><div>Jon</div>
<div><br><br><div class="gmail_quote">On Sun, Apr 11, 2010 at 4:05 PM, chovynz <span dir="ltr"><<a href="mailto:chovynz@gmail.com">chovynz@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
How about days? ;)<br>
<br>
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. <br>
<br>
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.<br>
<br>
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?<br>
<br>
Basically, how do you want us to use the tools we have? <br>
What is your vision for the Roadmap? <br>
Where do you want to go with OCAL?<br>
etcetc on big questions.<div class="im"><br>
<br>
<br>
<br>
On 12/04/2010 8:47 a.m., Jon Phillips wrote:
<blockquote type="cite">
<div dir="ltr">Ok, I'm game for trying/using blueprints...if no one
says anything in next couple of hours, lets start moving...<br>
<br>
Maybe I was the only one using the wiki anyway ;) <br>
<br>
Jon<br>
<br>
<div class="gmail_quote">On Sun, Apr 11, 2010 at 1:16 PM, chovynz <span dir="ltr"><<a href="mailto:chovynz@gmail.com" target="_blank">chovynz@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">I
prefer Launchpad. I think the wiki is not a good place for
bugtracking/blueprint stuff.<br>
Wiki is more for historic/discussion/FAQ/, I feel.<br>
However, I won't do anything on that until I hear a consensus. So,
sorry. No. Won't do it today. ;)<br>
<br>
Cheers<br>
<font color="#888888">Chovynz</font>
<div>
<div><br>
<br>
On 12/04/2010 8:11 a.m., Jon Phillips wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
Heya, we must decide. Are we going to use the launchpad blueprints or
the current OpenClipArt wiki?<br>
<br>
<a href="https://blueprints.launchpad.net/openclipart" target="_blank">https://blueprints.launchpad.net/openclipart</a><br>
<br>
vs<br>
<br>
<a href="http://openclipart.org/wiki/roadmap" target="_blank">http://openclipart.org/wiki/roadmap</a><br>
<br>
It seems that before we go over to 2.1, we should move completely to
one solution.<br>
<br>
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?<br>
<br>
Jon<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Jon Phillips<br><a href="http://rejon.org/">http://rejon.org/</a><br><a href="http://fabricatorz.com/">http://fabricatorz.com/</a><br><a href="http://status.net/">http://status.net/</a><br>
<a href="http://rejon.status.net">http://rejon.status.net</a> + skype: kidproto<br>+1.415.830.3884 (sf/global)<br>+86.134.3957.2035 (china)<br>
</div></div>