If someone else could edit the wiki (I can't, I haven't got edit
access to the wiki), then here is a report until Michael/anybody else
edits/replaces it.

Three most important issues to address in the move towards graduation:

  1. Make a release (stalled).
The licensing issues have been resolved, and build scripts have been
put into the repository. Documentation (see 2) is missing, after which
point we can finalize a commit suitable for release.
  2. Improve documentation.
This is currently scattered between the old WaveProtocol site, the
mailing list, and elsewhere. It needs to be pruned (of no-longer
relevant documentation), structured and put on the wiki.
  3. Increase community size.
We are lacking any contributors who are able to make/support large
code changes at the moment. A release should help increase wider
knowledge of the project, to hopefully bring in more development
support.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
None at this time. (Though see Shepard's notes).

How has the community developed since the last report?
The mailing list traffic continues to consist of new people asking
questions about setting-up/running a WIAB server. (Which could be
resolved by #2). Other than that, mostly stagnation.

How has the project developed since the last report?
Some progress towards a release (licensing) has been made.
Internationalization support has been added.

Ali

On 15 March 2013 16:13, Christian Grobmeier <grobme...@gmail.com> wrote:
> Please note: Matt (who is doing the report this period) has asked Wave
> to submit it before Friday evening - which is pretty close to now.
>
> Cheers
>
>
> On Fri, Mar 15, 2013 at 3:45 PM, Michael MacFadden
> <michael.macfad...@gmail.com> wrote:
>> I will write the report this weekend.
>>
>> On 3/15/13 7:38 AM, "Yuri Z" <vega...@gmail.com> wrote:
>>
>>>Anyway, is there anyone who wants to write the report?
>>>
>>>
>>>On Fri, Mar 15, 2013 at 2:26 PM, Vicente J. Ruiz Jurado
>>><v...@ourproject.org
>>>> wrote:
>>>
>>>> El 15/03/13 12:42, Upayavira escribió:
>>>> > The most important thing that needs to happen is a release. I think
>>>>this
>>>> > really needs to happen before the next board report (i.e. three months
>>>> > time). However, it would be much better for it to happen sooner, as it
>>>> > would be useful to see if a release actually draws in more interest.
>>>>And
>>>> > that's something the project needs.
>>>>
>>>> It's nice to know these priorities. I'm new in the Apache community and
>>>> as committer and this process is not very clear to me.
>>>>
>>>> > To follow this path, we need to see some change, and some growth.
>>>>Ideas
>>>> > beyond making a release (which needs to happen anyway) are welcome.
>>>>
>>>> As I said before, I can help creating a debian package that I think can
>>>> spread also the Wave use. I did the kune package [1], and it can be very
>>>> similar (even more simple). Yuri was interested on this issue also. My
>>>> problem with the debian package is that I can (and I know how to) create
>>>> an onejar package (with all the dependencies, that is, the
>>>> waveinabox-server.jar) but I don't know if this follow the Apache
>>>> guidelines.
>>>>
>>>> Other problem we have is documentation. IMHO, we'll be great to have
>>>> some waves in some server (eating your own dog food) with robots and
>>>> gadgets howtos, and similar stuff.
>>>>
>>>> Also, we'll help with Wave translation. We have translated kune in 16
>>>> languages thanks to a web translator, and I'll add the Wave strings so
>>>> our translators group can translate Wave also easily (without be a
>>>> developer).
>>>>
>>>> BR,
>>>> --
>>>> Vicente J. Ruiz Jurado
>>>>
>>>> http://comunes.org
>>>> http://ourproject.org
>>>> http://homes.ourproject.org/~vjrj/blog (@vjrj)
>>>>
>>>>  "Work like you don't need the money. Love like you've never been hurt.
>>>>  Dance like nobody's watching." [Satchel Paige]
>>>>
>>>> [1] https://gitorious.org/kune/trunk/trees/master/debian
>>>>
>>
>>
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de

Reply via email to