One more thing...the GNOME wiki articles themselves should be managed from a series of Git repositories. If the already are and I'm not aware that's great. Then you could integrate it into Redmine and managed everything from there. It makes perfect sense.
http://www.redmine.org/screenshots/scm_diff.png On Fri, Jun 20, 2014 at 5:38 PM, Alex G.S. <[email protected]> wrote: > How and why would "Basecamp, Trac or Redmine" help? Which specific >> features you consider critical are missing in our wiki or Bugzilla? > > > Specifically the ability to setup a sub-project and have issue tracking. > For example things like the "Annual Report 2013" could have been a > sub-project and each article could be an "feature" and people could then be > assigned or assign themselves to that "feature". If problems happened > during production "issue" tickets could be created and resolved. Then you > could have charts that would allow you to see how far along the project is. > > link: http://www.redmine.org/projects/redmine/wiki/Features > > That's more of what I'm talking about... > > > > On Fri, Jun 20, 2014 at 3:34 PM, Andre Klapper <[email protected]> wrote: > >> On Fri, 2014-06-20 at 14:09 -0400, Alex G.S. wrote: >> > After reading the comments and following several threads I've come to >> > realize that the one big problem we are all facing is a general state >> > of chaos. Something like Basecamp, Trac or Redmine would go a long >> > way to solving these problems. >> >> How and why would "Basecamp, Trac or Redmine" help? Which specific >> features you consider critical are missing in our wiki or Bugzilla? >> >> andre >> -- >> Andre Klapper | [email protected] >> http://blogs.gnome.org/aklapper/ >> >> _______________________________________________ >> engagement-list mailing list >> [email protected] >> https://mail.gnome.org/mailman/listinfo/engagement-list >> > >
_______________________________________________ engagement-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/engagement-list
