In general I think you can call for a vote any time you want and just
let people know that if they don't vote or give feedback that you plan
to move forward with your work. After doing that I think it's fair to
give a day or two of time for people to respond. The rules are pretty
flexible depending on the situation, but for larger features like
tagging I think it's better to be a little more cautious and try and get
more community involvement, rather than just moving forward on your own.
I am looking at the propsal again and I think you have all the right
stuff for the way tagging affects the backend, as far as data model and
manager and pojo changes. I think the very end of the proposal is a bit
lacking though, particularly in how tagging with affect the UI. I think
it would be helpful to start a subsection under 'Design' for 'Changes to
the UI' and list things there like ... what new urls are going to be
formed and how are they expected to work? exactly what methods are
being added to Model classes and how are they expected to work? what
new servlets would be needed and how will they work?
-- Allen
Elias Torres wrote:
I'm not sure how much time to give to folks for feedback before sending
an email asking for a vote. What do you think?
Allen Gilliland wrote:
I don't want to hold up your work, but we should probably get a little
more feedback on the proposal and some form of vote to make sure
everyone is on board.
You should also check with Dave that this is okay and won't disrupt the
3.0 release process.
-- Allen
Elias Torres wrote:
Folks,
I have begun writing some of the tagging support for Roller 3.1 and I
have a basic unit working. I've created WeblogEntryTagData and added
methods to WeblogEntryData to support Tagging. I've also written 10
tests in WeblogEntryTest.java and of course added support in the editing
UI to manage tags.
Is it ok if I start checking this in before my hard drive crashes?
-Elias
