Re: 3.18 topics: application revival



Matthias Clasen wrote:

Maybe we do something to improve this situation, from the release team
? Some ideas I had:

1) Patch review days - ask the community to spend a day focused just
on bugs and patches of one app, with the goal of working through the
backlog and making visible progress. In cases where maintainers have
gone missing, we may need to find volunteers to lead this ?

2) Call out "5 easy tasks" for an app. Provide some design guidance,
and promise the prospective contributors that we'll ensure timely
review.

3) Anything else ? I'm sure I had another idea, but blanking now...

As a support tool for us I still plan to work on activity monitoring
(what was started as https://people.gnome.org/~fpeters/health/ in a
previous hackfest).

For some applications we could also look at what's being produced in
other circles and see how to participate to existing apps instead of
starting or reviving our owns (Yorba, Elementary, or other small and
independant projects like lollypop).


Another topic we should discuss this cycle: Cutting dead wood from our
application list. The prime example here is empathy - nothing
significant has happened in empathy for a long time.

This is almost the same conversation than the other one, stalled or
stagnant, etc. how to put back some energy into this?  I think we
should include Empathy in the general efforts we have to do on apps.



        Fred


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]