Changes between Version 15 and Version 16 of SeaChange/WhatDevelopersWant

Timestamp:

Apr 13, 2011, 1:43:04 PM (13 years ago)

Author:

Christian Boos

Comment:

answer a few more items

SeaChange/WhatDevelopersWant

@@ -2 +2 @@
  '' A blackboard for ideas related to future directions'' 
 
-More seriously, this page is for drafting long term ideas and share the vision the Trac developers have.
+This page is for drafting long term ideas and share the vision the Trac developers have about the future directions of the project.
 
+See also those related resources:
  - for the actual coordination of on-going tasks, see TracDev/ToDo.
- - have an sneak preview of [ChristianBoos#NextSteps cboos' next steps]
- - see the topics currently discussed for the [[TracDev/ReleaseNotes/0.13|next major version 0.13]]
+ - have a sneak preview of [ChristianBoos#NextSteps cboos' next steps]
+ - see the topics currently discussed for the next major versions [[TracDev/ReleaseNotes/0.13|0.13]] and [[TracDev/ReleaseNotes/0.14|0.14]].
+
+Thanks to our editorial freedom, this page has also been hijacked by potential contributors asking questions or raising concerns...  for example:
 
 Need:
@@ -24 +27 @@
         }}}       
      a. lowering the barrier to entry [[br]]
-        We could achieve this by providing better docs, API docs, 
-        cleaner and simpler code
+        We could achieve this by providing better docs, API docs , 
+        cleaner and simpler code (ticket:10125#comment:15 has some good hints about this)
         {{{#!div style="background:#efe"
         Comment: When I started looking into Trac it kinda felt like development documentation is somewhere between minimal and completely missing for some areas, but I personally find the source code quite useful (its well documented and I found everything I needed so far). Yet I do think that setting-up API documentation can really help developing for Trac, while it shouldn't take too much effort - there must be plenty of API documentation generators for Python - shesek
         }}}
+           see TracDev/ApiDocs...
      a. motivating people to jump over the barrier [[br]]
          - the great new feature!
@@ -36 +40 @@
          - ?? Use more standard libraries. Templating has moved to Genshi, but maybe SQLAlchemy for DB backend?
          - ?? Highlight issues that should be easy for new people to fix
+           - see [query:?status=!closed&keywords=~bitesized]
          - ?? Google summer of code mentoring (requires time though)
  2. '''Core developers do not or cannot commit a lot of time to the project''' [[br]] 
@@ -63 +68 @@
     Well, WebAdmin was integrated. There was some attempt to do the same for 
     [TH:AccountManagerPlugin] (see also [../WhatUsersWant]), but see 3.
+      - see again ticket:10125#comment:15: getting some parts of the TH:XmlRpcPlugin into core?
     Note that some plugins will never be integrated or even bundled, due to 
     licensing issues (TracMercurial and [TH:GitPlugin]).
@@ -73 +79 @@
     This makes it possible to have some room between 
     ''strictly necessary for almost anyone using Trac (`trac.`)'' and
-    ''optional, must be 3^rd^ party.''
+    ''optional, must be 3rd party.''