- From: Doug Schepers <schepers@w3.org>
- Date: Sun, 25 Nov 2012 20:51:35 -0500
- To: Jonathan Garbee <jonathan@garbee.me>
- CC: public-webplatform@w3.org
Hi, Garbee- I don't think this is a step back at all. I think it's highly productive to step back and look at the simplest way we could accomplish our goals. I also agree with the goals you've laid out. I think this should be the primary focus of our discussion on Tuesday. Regarding the bug-tracker: While I agree with you that nobody (myself included) likes Bugzilla very much, we could host our own version of a more modern and better-configured Bugzilla as a stable stop-gap for our ultimate solution, which we could keep experimenting with. This would remove the problem of having to have a new account for filing bugs, and we could easily import all our old bugs. Thoughts? Regards- -Doug On 11/25/12 7:18 PM, Jonathan Garbee wrote: > I think this conversation has been kind-of messy so far. One of the > things brought up during the telecon two weeks ago was to do a table > showing what we were trying to do and what different pieces of software > would do towards those goals. That is a great idea and is going to be > done at some point. For now I'm putting testing software and figuring > things towards that out on hold for a bit. > > Let's try to simply list what the goals of centralizing things are first > and work our way forward from there. Yes, I do know this seems like a > huge step back after a couple thousand word emails; overall though I > think hopefully making things clearer by rebooting will help us all. So, > here is a quick list of what I think we should be trying to solve based > on what the original conversation was and then from a few things that > happened from the initial conversation: > > * Bug tracking on the WPD domain. --There was a bit of talk at launch > with people upset over needing yet another account and with this in > particular even requiring one on another domain; plus, I don't think too > many of us honestly like Bugzilla for our use-case. > * A way to track content revisions. --We have a handful of ways right > now to track edits and who is working on or should do what. > * A system for discussing content in detail outside of being a main part > of content. --Things like controversial topics or things people just > want some discussion on. > * Issues that people have with the content. --This could fall under > content revisions. I'm thinking specifically about people suggesting > ways of improving sentences or other grammatical things without actually > editing it themselves. Mostly what I see the current comment system > being used for, but not as effectively as we could have a system working. > > Are there any targets I missed in that list or you feel should be > changed? Let's get a target and why. Then worry about how to solve the > problem later in discussion. > > Thanks, > -Garbee >
Received on Monday, 26 November 2012 01:51:43 UTC