[Maria-docs] TODO Tracking
Hi all, I've been accumulating a pretty big list of things to do in the KB. To get more people involved, and people working together, it's really important to get these things public. A prominent "Contribute" page could link to the list, giving people a sense of what they can do. Two options: 1) Keep a list of stuff in a wiki. The KB itself is a wiki, so the list could go write in the KB. 2) Use an issue tracker. We could use LP, since everything else is happening there anyway. We'd have to create a project on LP. I don't know how happy LP is with projects that aren't backed by an actual bzr repository. Thoughts?
Hi, Shaun! On Dec 01, Shaun McCance wrote:
Hi all,
I've been accumulating a pretty big list of things to do in the KB. To get more people involved, and people working together, it's really important to get these things public. A prominent "Contribute" page could link to the list, giving people a sense of what they can do.
Two options:
1) Keep a list of stuff in a wiki. The KB itself is a wiki, so the list could go write in the KB.
2) Use an issue tracker. We could use LP, since everything else is happening there anyway. We'd have to create a project on LP. I don't know how happy LP is with projects that aren't backed by an actual bzr repository.
Thoughts?
We're moving to Jira, so you only need an intermediate solution until we're done. Regards, Sergei
--- Gio 1/12/11, Shaun McCance <shaunm@gnome.org> ha scritto: Two options: 1) Keep a list of stuff in a wiki. The KB itself is a wiki, so the list could go write in the KB. 2) Use an issue tracker. We could use LP, since everything else is happening there anyway. We'd have to create a project on LP. I don't know how happy LP is with projects that aren't backed by an actual bzr repository. Thoughts? I suggest the second option. If people will contribute to the KB, extra info will be needed (pages which need to be revised, assignees, "bug reports", comments, etc), and a single wiki page may not be the best way to store that info. Also, I think that making the KB source code avaible as Free Software would encourage people to contribute it. Federico
On Fri, 2011-12-02 at 11:18 +0000, Federico Razzoli wrote:
--- Gio 1/12/11, Shaun McCance <shaunm@gnome.org> ha scritto: Two options:
1) Keep a list of stuff in a wiki. The KB itself is a wiki, so the list could go write in the KB.
2) Use an issue tracker. We could use LP, since everything else is happening there anyway. We'd have to create a project on LP. I don't know how happy LP is with projects that aren't backed by an actual bzr repository.
Thoughts?
I suggest the second option. If people will contribute to the KB, extra info will be needed (pages which need to be revised, assignees, "bug reports", comments, etc), and a single wiki page may not be the best way to store that info.
I think I agree with you in general, but if there's going to be a JIRA instance soon we can use, setting up a different issue tracker seems like a lot of wasted work. We'll just end up with a perpetually dead tracker that will gather Google juice and distract contributors. What I'd suggest is to create a Contribute page on the KB and include a list of tasks as a section on that page. When JIRA is set up, we can move all the tasks there, and link there from the Contribute page. No dead trackers, no extra pages that can gather links only to 404. -- Shaun
On Fri, 02 Dec 2011 13:03:51 -0500 Shaun McCance <shaunm@gnome.org> wrote: <snip> Shaun> I think I agree with you in general, but if there's going to be Shaun> a JIRA instance soon we can use, setting up a different issue Shaun> tracker seems like a lot of wasted work. We'll just end up with Shaun> a perpetually dead tracker that will gather Google juice and Shaun> distract contributors. True. Shaun> What I'd suggest is to create a Contribute page on the KB and Shaun> include a list of tasks as a section on that page. When JIRA is Shaun> set up, we can move all the tasks there, and link there from the Shaun> Contribute page. No dead trackers, no extra pages that can Shaun> gather links only to 404. This is a good idea. As per a previous email, I've taken the contribution information from the about page and moved it to a separate page: http://kb.askmonty.org/en/contributing-to-the-askmonty-knowledgebase I've also featured the article (so it appears on the main page). Please create a section at the bottom of that page for tasks and let's start populating it. :) Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
--- Sab 3/12/11, Daniel Bartholomew <dbart@montyprogram.com> ha scritto: Da: Daniel Bartholomew <dbart@montyprogram.com> Oggetto: Re: [Maria-docs] R: TODO Tracking A: "Shaun McCance" <shaunm@gnome.org> Cc: "Federico Razzoli" <federico_raz@yahoo.it>, "Maria Docs" <maria-docs@lists.launchpad.net> Data: Sabato 3 dicembre 2011, 05:17 On Fri, 02 Dec 2011 13:03:51 -0500 Shaun McCance <shaunm@gnome.org> wrote: <snip> Shaun> I think I agree with you in general, but if there's going to be Shaun> a JIRA instance soon we can use, setting up a different issue Shaun> tracker seems like a lot of wasted work. We'll just end up with Shaun> a perpetually dead tracker that will gather Google juice and Shaun> distract contributors. True. I agree too; if you are going to move to a new bug tracker, KB tasks should not be added to the old one. This is a good idea. As per a previous email, I've taken the contribution information from the about page and moved it to a separate page: http://kb.askmonty.org/en/contributing-to-the-askmonty-knowledgebase I'm going to translate the page into italian, except for the taks section (duplication is bad, and people need to read/write in english to contribute). Is it OK? Federico
On Sat, 3 Dec 2011 10:51:01 +0000 (GMT) Federico Razzoli <federico_raz@yahoo.it> wrote: Federico> http://kb.askmonty.org/en/contributing-to-the-askmonty-knowledgebase Federico> I'm going to translate the page into italian, except for the Federico> taks section (duplication is bad, and people need to Federico> read/write in english to contribute). Is it OK? Yes, that sounds good. And instead of a tasks section, can you just tell people to go to the English version of the page to see the list? Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
On Fri, 2 Dec 2011 23:17:04 -0500 Daniel Bartholomew <dbart@montyprogram.com> wrote: <snip> Shaun> What I'd suggest is to create a Contribute page on the Shaun> KB and include a list of tasks as a section on that Shaun> page. When JIRA is set up, we can move all the tasks Shaun> there, and link there from the Contribute page. No dead Shaun> trackers, no extra pages that can gather links only to Shaun> 404. Daniel> This is a good idea. As per a previous email, I've taken the Daniel> contribution information from the about page and moved it to a Daniel> separate page: Daniel> Daniel> http://kb.askmonty.org/en/contributing-to-the-askmonty-knowledgebase Daniel> Daniel> I've also featured the article (so it appears on the main page). Daniel> Daniel> Please create a section at the bottom of that page for tasks Daniel> and let's start populating it. :) Shaun, I just noticed that you had created a Contribute page here: http://kb.askmonty.org/en/meta-contribute If it's ok with you, I'd like to merge your text into the page I created and then delete the meta-contribute page. Let me know if you want to do it instead. Thanks. -- Daniel Bartholomew MariaDB - http://mariadb.org Monty Program - http://montyprogram.com AskMonty Knowledgebase - http://kb.askmonty.org
participants (4)
-
Daniel Bartholomew -
Federico Razzoli -
Sergei Golubchik -
Shaun McCance