commitfest.postgresql.org

[Alvaro Herrera-7]

Brendan Jurd escribió:

> Short answer: I could bring across the old commitfests but it would
> take a couple hours at best per commitfest and result in little bits
> of data loss here and there.  I think we might be better off just
> leaving the closed commitfests up on the wiki, and putting a notice on
> the app saying "commitfests prior to July 2009 can be found at
> wiki.postgresql.org".

Agreed; if it requires manual work let's leave them in the wiki.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Tom Lane-2]

Brendan Jurd <direvus@...> writes:
> We're now about a week away from the start of the July 2009
> commitfest, and we need to make a decision about whether to start
> using http://commitfest.postgresql.org to manage it, or punt to the
> next commitfest and continue to use the wiki for July.

While reorganizing my bookmarks for this I realized that there is a
fairly significant bit of functionality that's entirely missing from
the new app.  With the wiki page, you could conveniently see what had
been done lately by examining the page history.  I don't see any
equivalent capability in the new app.  I find this fairly significant,
as evidenced by the fact that I'd gone so far as to set up a bookmark
for the history view.  I'm not particularly wedded to the wiki page
history in terms of what it looks like or how it functions, but I do
feel a need to know what other people have done recently.

                        regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Dickson S. Guedes-4]

Em Thu, 09 Jul 2009 14:16:41 -0300, Tom Lane <tgl@...> escreveu:
> I'm not particularly wedded to the wiki page
> history in terms of what it looks like or how it functions, but I do
> feel a need to know what other people have done recently.

May be the new app could have a page with a filterable table log with some  
important columns like "who" do "what" on "where" and "when".

This could help, maybe with a RSS in that (like in git).

[]s
Dickson S. Guedes
http://pgcon.postgresql.org.br
http://www.postgresql.org.br

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Brendan Jurd]

2009/7/10 Tom Lane <tgl@...>:
> While reorganizing my bookmarks for this I realized that there is a
> fairly significant bit of functionality that's entirely missing from
> the new app.  With the wiki page, you could conveniently see what had
> been done lately by examining the page history.  I don't see any
> equivalent capability in the new app.

You're right, the app currently lacks a view for this.

And while it would be pretty easy to add a page that just lists the
most recent comments in descending creation order, that would not show
things like

 * patches being committed/rejected/punted;
 * patches changed to a different subsection;
 * changes to a patch's short name;
 * edits to existing comments.

We don't AFAIK collect data about these events.  However, we could
have certain actions trigger the creation of an automated comment
(e.g., "Status changed to Committed by petere") and let the
aforementioned comment view suffice for a "history".

Cheers,
BJ

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Joshua Tolley]

On Thu, Jul 09, 2009 at 02:35:04PM -0300, Dickson S. Guedes wrote:
> This could help, maybe with a RSS in that (like in git).

+1 for the RSS feed, if only because I think it sounds neat :)

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

[Robert Haas]

On Jul 9, 2009, at 12:16 PM, Tom Lane <tgl@...> wrote:

> Brendan Jurd <direvus@...> writes:
>> We're now about a week away from the start of the July 2009
>> commitfest, and we need to make a decision about whether to start
>> using http://commitfest.postgresql.org to manage it, or punt to the
>> next commitfest and continue to use the wiki for July.
>
> While reorganizing my bookmarks for this I realized that there is a
> fairly significant bit of functionality that's entirely missing from
> the new app.  With the wiki page, you could conveniently see what had
> been done lately by examining the page history.  I don't see any
> equivalent capability in the new app.  I find this fairly significant,
> as evidenced by the fact that I'd gone so far as to set up a bookmark
> for the history view.  I'm not particularly wedded to the wiki page
> history in terms of what it looks like or how it functions, but I do
> feel a need to know what other people have done recently

I'll fix this. Give me a couple days; my Internet access here at the  
family vacation spot is not compatible with "git push".

...Robert

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Josh Berkus]

> We don't AFAIK collect data about these events.  However, we could
> have certain actions trigger the creation of an automated comment
> (e.g., "Status changed to Committed by petere") and let the
> aforementioned comment view suffice for a "history".

Can you put in a simple event-recording trigger for all changes?  We can
dress it up for easy viewing later, but if the data isn't collected, it
will be impossible to recreate.

--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Tom Lane-2]

Josh Berkus <josh@...> writes:
>> We don't AFAIK collect data about these events.  However, we could
>> have certain actions trigger the creation of an automated comment
>> (e.g., "Status changed to Committed by petere") and let the
>> aforementioned comment view suffice for a "history".

> Can you put in a simple event-recording trigger for all changes?

+1.  Just add an event log table.  I think we'll wish we had one later.

                        regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Brendan Jurd]

2009/7/10 Josh Berkus <josh@...>:

>
>> We don't AFAIK collect data about these events.  However, we could
>> have certain actions trigger the creation of an automated comment
>> (e.g., "Status changed to Committed by petere") and let the
>> aforementioned comment view suffice for a "history".
>
> Can you put in a simple event-recording trigger for all changes?  We can
> dress it up for easy viewing later, but if the data isn't collected, it will
> be impossible to recreate.
>

I could, but a db trigger would have no awareness of which user made
the change.  That would make the information substantially less useful
IMO.

I've got access to the database but I'm not in a position to make
changes to the app frontend.  I'm therefore inclined to wait the
prophesied couple days for Robert's proper fix for this problem than
dropping in a trigger which will only tell us part of the story.

Bear in mind that CF activity over the past week has been in the realm
of 0-4 changes per 24 hours, so it's not like we are talking about
huge amounts of throughput here.  Making up the bulk of those changes
were new patches coming in (which involves adding a comment so the
change is already tracked) and patches getting committed (which is
stored in -hackers and version control anyway).

Cheers,
BJ

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Tom Lane-2]

Brendan Jurd <direvus@...> writes:
> Bear in mind that CF activity over the past week has been in the realm
> of 0-4 changes per 24 hours, so it's not like we are talking about
> huge amounts of throughput here.

Well, it'll be more once commitfest actually starts, but in any case
it's not going to be enough to make a log table be a resource hog.

                        regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Decibel!]

On Jul 9, 2009, at 12:35 PM, Brendan Jurd wrote:
> We don't AFAIK collect data about these events.  However, we could
> have certain actions trigger the creation of an automated comment
> (e.g., "Status changed to Committed by petere") and let the
> aforementioned comment view suffice for a "history".


Our main system at work does that; any kind of status is stored as a  
raw, text "note". It sucks. It makes trying to query for specific  
kinds of events difficult, and it wastes a bunch of space.

It's a lot better to record machine-readable information for machine-
created events. If you want to present it all as one, I suggest a  
union view that turns the machine-understood data into a human-
understandable text format.
--
Decibel!, aka Jim C. Nasby, Database Architect  decibel@...
Give your computer some brain candy! www.distributed.net Team #1828



--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Josh Berkus]

 >>  I think we might be better off just
>> leaving the closed commitfests up on the wiki, and putting a notice on
>> the app saying "commitfests prior to July 2009 can be found at
>> wiki.postgresql.org".

+1.  That's why we're switching technogies at the beginning of a dev cycle.


--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[Robert Haas]

On Thu, Jul 9, 2009 at 2:20 PM, Robert Haas<robertmhaas@...> wrote:

> On Jul 9, 2009, at 12:16 PM, Tom Lane <tgl@...> wrote:
>
>> Brendan Jurd <direvus@...> writes:
>>>
>>> We're now about a week away from the start of the July 2009
>>> commitfest, and we need to make a decision about whether to start
>>> using http://commitfest.postgresql.org to manage it, or punt to the
>>> next commitfest and continue to use the wiki for July.
>>
>> While reorganizing my bookmarks for this I realized that there is a
>> fairly significant bit of functionality that's entirely missing from
>> the new app.  With the wiki page, you could conveniently see what had
>> been done lately by examining the page history.  I don't see any
>> equivalent capability in the new app.  I find this fairly significant,
>> as evidenced by the fact that I'd gone so far as to set up a bookmark
>> for the history view.  I'm not particularly wedded to the wiki page
>> history in terms of what it looks like or how it functions, but I do
>> feel a need to know what other people have done recently
>
> I'll fix this. Give me a couple days; my Internet access here at the family
> vacation spot is not compatible with "git push".

OK, this is a little bit quick-and-dirty, and I'm sure I'll get some,
ah, gentle suggestions for improvement, but I've added an activity log
to the app.

...Robert

--
Sent via pgsql-hackers mailing list (pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers