Changes between Version 5 and Version 6 of SeaChange/WhatDevelopersWant

Timestamp:

Apr 14, 2010, 5:47:50 PM (14 years ago)

Author:

Christian Boos

Comment:

add a link to my page

SeaChange/WhatDevelopersWant

@@ -1 +1 @@
 = Developers' Corner =
- '' A blackboard for ideas related to future directions''
+ '' A blackboard for ideas related to future directions'' ,,(or: ''How do we bribe the aliens so that we can reach milestone:2.0?''),,
 
-(or, ''How do we bribe the aliens so that we can reach milestone:2.0?'')
+More seriously, this page is for drafting long term ideas and share the vision the Trac developers have.
 
-More seriously, this is more for drafting long term ideas; 
-for the actual coordination of on-going tasks, see TracDev/ToDo.
+ - for the actual coordination of on-going tasks, see TracDev/ToDo.
+ - have an sneak preview of [ChristianBoos#NextSteps cboos' next steps]
+
 
 == Development Process Issues ==
@@ -14 +15 @@
     How?
         {{{#!div style="background:#efe"
-        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.
+        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"
@@ -37 +38 @@
         }}}
  3. '''Frequently requested features do not get implemented''' [[br]] 
-    Big features (e.g. MultiProjectSupport) first need to have a developer really   
+    Big features (e.g. MultipleProjectSupport) first need to have a developer really   
     needing the feature, as it can't be done without some kind of deep involvement.
     See 1.2.