Changes between Version 4 and Version 5 of SeaChange/WhatDevelopersWant

Timestamp:

Mar 30, 2010, 5:39:44 AM (14 years ago)

Author:

Rowan Wookey <admin@…>

Comment:

—

SeaChange/WhatDevelopersWant

@@ -16 +16 @@
         Comment: Just look at the history of #2456. People cared, wrote patches, discussed the issue. But in the end nothing changed despite the fact that trac doesnt adhere to its design principles in that area (Users not managed via pluggable Components/Relations) The ticket is '''4 years old'''. There are few comments from team members and virtually no information what problems prevent this to move forward. People got frustrated, wrote competing implementations/plugins or gave up and moved on. I think it's worth analyzing what went wrong here.
         }}}
+        {{{#!div style="background:#efe"
+        Comment: ActiveState now use trac commercially (http://firefly.activestate.com) maybe the core developers could get active state to pitch in?
+        }}}
+
      1. lowering the barrier to entry [[br]]
         We could achieve this by providing better docs, API docs, 
@@ -29 +33 @@
  2. '''Core developers do not or cannot commit a lot of time to the project''' [[br]] 
     Whip them? Otherwise, see 1.
+        {{{#!div style="background:#efe"
+        Comment: In theory they don't need to, if the community can write patches and test them, then all the core developers need to do is commit to svn.
+        }}}
  3. '''Frequently requested features do not get implemented''' [[br]] 
     Big features (e.g. MultiProjectSupport) first need to have a developer really