whube-core team mailing list archive

[matthew byers <faintstlsaint@xxxxxxxxx>]

This issue occured to me today as i was going through some whube pages in my
bookmarks and realized i had over 6 seperate pages of whube stuff trying to
juggle. Thus the idea of project management came up and tenach felt the same
way i did. Though i dont speak for everyone i feel as if those who are not
direct devs of whube are not in the loop as to the "status" of whube. And i
really dont know when its my turn as the wiki guy to jump in and turn out
some docs. With some sort of project management system we all can be on one
accord  as tenach has already described. Doing some research i came across
redmine and though i have never used it it looks really feature rich.
http://www.redmine.org/
http://www.redmine.org/wiki/redmine/Features
With redmine we manage repos from git and other version controls, setup
wiki/docs, track bugs and whube feature additions, assign teams/roles and we
do this all in one location as they get organized and setup then when they
are all pretty and ready for the world we migrate them to their appropriate
web pages: ie: bugs.whube, docs.whube, etc. We already have a project
manager so he can head up the project management system! Just my
thoughts....


On Sat, Sep 11, 2010 at 5:19 PM, Thomas Plastino Martin <tenach@xxxxxxxxx>wrote:

> Hello everyone,
>
> We need to organize Whube in a serious manner.  At present we do not have a
> solid goal for the future past our list for DD.  This team is growing and
> now we're in need of some sort of system in place where we can all stay 'in
> the loop'.  So far we have docs.whube, bugs.whube and Launchpad.  I think
> that we need to start actively putting our team organization together, so
> that we all know who is doing what, where we're going, etc.
>
> stlsaint suggested using a project management system like Pier.  I have
> only really worked with Trac and Collabtiv, both of which I am not too fond
> of (I prefer Collabtiv over Trac any day though).  I think it might be a
> good idea, though I was under the impression we were going to use Launchpad
> for team stuff, such as milestones/blueprints/whatnot.  However, this
> confuses me. Launchpad is confusing too.
>
> Anyway.  What are we going to do?
>
> * We need to have an outline for the future of Whube.
> * We should state clearly how we are going to use Launchpad, and use it as
> such.
> * There is more, but I do not remember off the top of my head at the
> moment.
>
> Whube has potential to be awesome, we just need to realize the path and
> figure out exactly how we are going to go about it.  I think that the days
> of freeform coding are (mostly) over, at least until we have a solid
> understanding of everyone's contributions.
>
> I'd love to hear your thoughts on this.  Hopefully I'm not way off base
> with this.
>
> Thanks,
>
> Thomas Plastino Martin
> https://launchpad.net/~tenach <https://launchpad.net/%7Etenach>
> http://tenach.net
>
> _______________________________________________
> Mailing list: https://launchpad.net/~whube-core
> Post to     : whube-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~whube-core
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
God Bless