Commit digest

[duck-3]

We have a lot of modules and commits that are tracked only if they where
a ticked request or something that finished in module change log. And
again this is something too much developer closed overview. What about
to start publishing a weekly overview on Planet Horde of the development
activity like KDE's commit digests with just a short list of what
significant changed in last week. For example tickets solved with links
to tickets, new features that should be exposed like allow embedding of
Kronolith's calendar blocks in external websites etc.

Duck


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Jan Schneider]

Zitat von duck <duck@...>:

> We have a lot of modules and commits that are tracked only if they where
> a ticked request or something that finished in module change log. And
> again this is something too much developer closed overview. What about
> to start publishing a weekly overview on Planet Horde of the development
> activity like KDE's commit digests with just a short list of what
> significant changed in last week. For example tickets solved with links
> to tickets, new features that should be exposed like allow embedding of
> Kronolith's calendar blocks in external websites etc.

I'm against commit digest since they would include too much useless  
information, and I don't see anyone having enough time to compile them  
manually. But I agree that the ongoing development should be  
communicated much better.

As a first step I updated a few applications' news on the website. We  
should generate a feed from those and add it to Planet.

We already have feeds for closed tickets per application on the  
website, but a monthly or weekly summary would be nice too. This could  
even be implemented as a general Whups feature, alternatively  
available as a feed that could be added to Planet again.

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Chuck Hagenbuch]

Quoting duck <duck@...>:

> We have a lot of modules and commits that are tracked only if they where
> a ticked request or something that finished in module change log. And
> again this is something too much developer closed overview. What about
> to start publishing a weekly overview on Planet Horde of the development
> activity like KDE's commit digests with just a short list of what
> significant changed in last week. For example tickets solved with links
> to tickets, new features that should be exposed like allow embedding of
> Kronolith's calendar blocks in external websites etc.

Do you see this as something compiled by hand (by a human), or  
generated automatically? I agree with Jan that an automatic one would  
be a lot of noise, and while I can certainly see the value of a weekly  
summary written by a human, it's a non-trivial commitment to do it.

-chuck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[duck-3]

On Thu, 2008-08-21 at 22:54 -0400, Chuck Hagenbuch wrote:

> Quoting duck <duck@...>:
>
> > We have a lot of modules and commits that are tracked only if they where
> > a ticked request or something that finished in module change log. And
> > again this is something too much developer closed overview. What about
> > to start publishing a weekly overview on Planet Horde of the development
> > activity like KDE's commit digests with just a short list of what
> > significant changed in last week. For example tickets solved with links
> > to tickets, new features that should be exposed like allow embedding of
> > Kronolith's calendar blocks in external websites etc.
>
> Do you see this as something compiled by hand (by a human), or  
> generated automatically? I agree with Jan that an automatic one would  
> be a lot of noise, and while I can certainly see the value of a weekly  
> summary written by a human, it's a non-trivial commitment to do it.

Of course would be nicer to see something wrote by human with
explanation of some changes. But as we are all always out of time, I
guess that a cron job would be a good start. In the automatic process we
could add:

      * a list and links to all closed tickets
      * links to tickets that has some new related commits (to show that
        we are actually working on them)
      * a combined change log updates
      * maybe wiki (documentation) pages that were updated
       
Duck


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Jan Schneider]

Zitat von duck <duck@...>:

> On Thu, 2008-08-21 at 22:54 -0400, Chuck Hagenbuch wrote:
>> Quoting duck <duck@...>:
>>
>> > We have a lot of modules and commits that are tracked only if they where
>> > a ticked request or something that finished in module change log. And
>> > again this is something too much developer closed overview. What about
>> > to start publishing a weekly overview on Planet Horde of the development
>> > activity like KDE's commit digests with just a short list of what
>> > significant changed in last week. For example tickets solved with links
>> > to tickets, new features that should be exposed like allow embedding of
>> > Kronolith's calendar blocks in external websites etc.
>>
>> Do you see this as something compiled by hand (by a human), or
>> generated automatically? I agree with Jan that an automatic one would
>> be a lot of noise, and while I can certainly see the value of a weekly
>> summary written by a human, it's a non-trivial commitment to do it.
>
> Of course would be nicer to see something wrote by human with
> explanation of some changes. But as we are all always out of time, I
> guess that a cron job would be a good start. In the automatic process we
> could add:
>
>       * a list and links to all closed tickets

Agreed, as long as we limit this to "Resolved" tickets, i.e. no  
Reject, Not A Bug, Duplicate, etc.

>       * links to tickets that has some new related commits (to show that
>         we are actually working on them)

I'm not sure about that. People interested in certain tickets can  
already watch or subscribe to them, and we track commits for tickets.  
Tickets being worked on are probably not near as interesting as closed  
tickets.

>       * a combined change log updates

Do you mean diffs for CHANGES files? Good idea.

>       * maybe wiki (documentation) pages that were updated

Interesting, but probably again too noisy to be really useful.

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Eric Jon Rostetter]

Quoting duck <duck@...>:

>> Do you see this as something compiled by hand (by a human), or
>> generated automatically? I agree with Jan that an automatic one would
>> be a lot of noise, and while I can certainly see the value of a weekly
>> summary written by a human, it's a non-trivial commitment to do it.
>
> Of course would be nicer to see something wrote by human with
> explanation of some changes. But as we are all always out of time, I
> guess that a cron job would be a good start. In the automatic process we
> could add:

Could setup an automatic process which emails to a real person (maybe me,
maybe not) who then edits it by hand (remove unimportant stuff, add
comments and stuff, etc) and then posts it somehow.

Best of both worlds, so to speak...

--
Eric Rostetter
The Department of Physics
The University of Texas at Austin

This message is provided "AS IS" without warranty of any kind,
either expressed or implied.  Use this message at your own risk.

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Chuck Hagenbuch]

I've summarized the ideas in this thread here:
http://wiki.horde.org/Project/HordeWeb#toc4

If anyone wants to work on these now that's great, but I wanted to  
make sure the ideas weren't lost.

-chuck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[duck-3]

On Fri, 2008-08-22 at 14:31 +0200, Jan Schneider wrote:
> Zitat von duck <duck@...>:
>
> > On Thu, 2008-08-21 at 22:54 -0400, Chuck Hagenbuch wrote:
> >> Quoting duck <duck@...>:
> >>
> >       * a combined change log updates
>
> Do you mean diffs for CHANGES files? Good idea.
Yes. A list off all changes from all modules.

>
> >       * maybe wiki (documentation) pages that were updated
>
> Interesting, but probably again too noisy to be really useful.

Of course a page will be listed only once with last change log. Maybe we
can just add the info of how many changes where made or better the
number of lines changed. Both is already possible with current available
API calls. I added the missing gerRecentChanges call in a patch at
http://bugs.horde.org/ticket/7230.

Duck


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[duck-3]

On Fri, 2008-08-22 at 23:20 -0400, Chuck Hagenbuch wrote:
> I've summarized the ideas in this thread here:
> http://wiki.horde.org/Project/HordeWeb#toc4
>
> If anyone wants to work on these now that's great, but I wanted to  
> make sure the ideas weren't lost.

Maybe I can do something on making Whups publishing needed details. But
I am not so familiar with it so I must take some time to get used to. In
the wile I am asking if someone can update Whups phpDOCs. As are mainly
not existing and making hare me to understand it. At least the API calls
should be commented correctly to pass the reflactor.

Duck


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Chuck Hagenbuch]

Quoting duck <duck@...>:

> Maybe I can do something on making Whups publishing needed details. But
> I am not so familiar with it so I must take some time to get used to. In
> the wile I am asking if someone can update Whups phpDOCs. As are mainly
> not existing and making hare me to understand it. At least the API calls
> should be commented correctly to pass the reflactor.

I just took a pass through whups/lib/api.php adding phpdoc. If you  
have further questions, please just keep poking the list. :)

Thanks,
-chuck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[duck-3]

On Tuesday 26 August 2008 06:39:59 Chuck Hagenbuch wrote:

> Quoting duck <duck@...>:
> > Maybe I can do something on making Whups publishing needed details. But
> > I am not so familiar with it so I must take some time to get used to. In
> > the wile I am asking if someone can update Whups phpDOCs. As are mainly
> > not existing and making hare me to understand it. At least the API calls
> > should be commented correctly to pass the reflactor.
>
> I just took a pass through whups/lib/api.php adding phpdoc. If you
> have further questions, please just keep poking the list. :)
>

Looking for a way to list desired states cross queues I created a feed based
on the search functionality. I purpose to add a feed icon in the results
renderer too, so you can just click to add search results as a feed to you
feed aggregator.  After this will be commited I will implement the date
criteria.

http://bugs.horde.org/ticket/7259

Duck


--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Chuck Hagenbuch]

Quoting Duck <duck@...>:

> Looking for a way to list desired states cross queues I created a feed based
> on the search functionality. I purpose to add a feed icon in the results
> renderer too, so you can just click to add search results as a feed to you
> feed aggregator.  After this will be commited I will implement the date
> criteria.

Both of those sound good - the feed is committed now.

-chuck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[duck-3]

I enlarged the search mechanism (http://bugs.horde.org/ticket/7274) to accept
dates as criteria. So now we can have a feed on planet.horde.org with resolved
tickets cross queues in the last time slice. And of course now we have all we
needed to prepare a basic automated "commit digest".

I guess that it will be better to leave the automations script every Sunday
night so we get a fresh post in on Monday morning. And leave developers to
comment commits or better to post now blogs with explanations and related
activities.

Duck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...

[Chuck Hagenbuch]

Quoting Duck <duck@...>:

> I enlarged the search mechanism (http://bugs.horde.org/ticket/7274) to accept
> dates as criteria. So now we can have a feed on planet.horde.org  
> with resolved
> tickets cross queues in the last time slice. And of course now we have all we
> needed to prepare a basic automated "commit digest".
>
> I guess that it will be better to leave the automations script every Sunday
> night so we get a fresh post in on Monday morning. And leave developers to
> comment commits or better to post now blogs with explanations and related
> activities.

We still need one more piece (that automation bit) to compile posts:
http://bugs.horde.org/ticket/7284

-chuck

--
Horde developers mailing list - Join the hunt: http://horde.org/bounties/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: dev-unsubscribe@...