Thread: List of Auxiliary Projects
Hello,
following a discussion how a number of not-so-known PostgreSQL projects can be made more visible, attached is a first draft to list them on the website.
The draft lists three projects (pgweb, pgeu-system, pglister) as an example, and moves the new site under "Community". More projects with more description and contact details should be added, of course.
The purpose of this patch is to see if "Community" is the right place for this kind of information, and also what other projects and details should be included.
Thanks
--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project
Attachment
On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: > > Hello, > > following a discussion how a number of not-so-known PostgreSQL projects > can be made more visible, attached is a first draft to list them on the > website. > > The draft lists three projects (pgweb, pgeu-system, pglister) as an > example, and moves the new site under "Community". More projects with > more description and contact details should be added, of course. Seems like a good way to get people more involved. > The purpose of this patch is to see if "Community" is the right place > for this kind of information, and also what other projects and details > should be included. Are there any HTML templates? I only see the URL added in the context. Jonathan
Attachment
On 01/02/2020 00:37, Jonathan S. Katz wrote: > On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >> Hello, >> >> following a discussion how a number of not-so-known PostgreSQL projects >> can be made more visible, attached is a first draft to list them on the >> website. >> >> The draft lists three projects (pgweb, pgeu-system, pglister) as an >> example, and moves the new site under "Community". More projects with >> more description and contact details should be added, of course. > Seems like a good way to get people more involved. That is the goal, yes. >> The purpose of this patch is to see if "Community" is the right place >> for this kind of information, and also what other projects and details >> should be included. > Are there any HTML templates? I only see the URL added in the context. The patch adds the page to pgweb (first part), and adds the website itself (second part). Or am I missing something? Regards, -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
On 01/02/2020 00:37, Jonathan S. Katz wrote: > On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >> Hello, >> >> following a discussion how a number of not-so-known PostgreSQL projects >> can be made more visible, attached is a first draft to list them on the >> website. >> >> The draft lists three projects (pgweb, pgeu-system, pglister) as an >> example, and moves the new site under "Community". More projects with >> more description and contact details should be added, of course. > Seems like a good way to get people more involved. > >> The purpose of this patch is to see if "Community" is the right place >> for this kind of information, and also what other projects and details >> should be included. > Are there any HTML templates? I only see the URL added in the context. Actually, you are right. And the second part in my initial email just repeated the "contexts.py" file, instead of adding the correct file. Attached a new patch. Regards, -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
Attachment
On 1/31/20 7:24 PM, Andreas 'ads' Scherbaum wrote: > On 01/02/2020 00:37, Jonathan S. Katz wrote: >> On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >>> Hello, >>> >>> following a discussion how a number of not-so-known PostgreSQL projects >>> can be made more visible, attached is a first draft to list them on the >>> website. >>> >>> The draft lists three projects (pgweb, pgeu-system, pglister) as an >>> example, and moves the new site under "Community". More projects with >>> more description and contact details should be added, of course. >> Seems like a good way to get people more involved. >> >>> The purpose of this patch is to see if "Community" is the right place >>> for this kind of information, and also what other projects and details >>> should be included. >> Are there any HTML templates? I only see the URL added in the context. > > Actually, you are right. And the second part in my initial email just > repeated the "contexts.py" file, instead of adding the correct file. > Attached a new patch. OK, that makes much more sense ;) Feedback / bikeshedding: - I'd recommend putting the pith of the content in a subsection under "Developers". I don't see any issue linking to it from the community section (and perhaps rewriting the community page a bit to link to more of the "contributing areas", but the page is more about ways you can develop around things in PostgreSQL - I'm not sure how I feel about the term "Auxiliary" - it's not used so much any more and definitely prone to misspellings. Perhaps "Related Projects"? - I like the overall layout of the page and how there is content around each project. I think it's a good start. Thanks, Jonathan
Attachment
On Sat, Feb 1, 2020 at 1:51 AM Andreas 'ads' Scherbaum <ads@pgug.de> wrote: > > > Hello, > > following a discussion how a number of not-so-known PostgreSQL projects can be made more visible, attached is a first draftto list them on the website. > > The draft lists three projects (pgweb, pgeu-system, pglister) as an example, and moves the new site under "Community".More projects with more description and contact details should be added, of course. > > The purpose of this patch is to see if "Community" is the right place for this kind of information, and also what otherprojects and details should be included. So, what is a project ? Useful extensions, local pg resources, propaganda projects, educational sites, books, ... > > > Thanks > > -- > Andreas 'ads' Scherbaum > German PostgreSQL User Group > European PostgreSQL User Group - Board of Directors > Volunteer Regional Contact, Germany - PostgreSQL Project -- Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
On 01/02/2020 20:30, Oleg Bartunov wrote: > On Sat, Feb 1, 2020 at 1:51 AM Andreas 'ads' Scherbaum <ads@pgug.de> wrote: >> >> Hello, >> >> following a discussion how a number of not-so-known PostgreSQL projects can be made more visible, attached is a firstdraft to list them on the website. >> >> The draft lists three projects (pgweb, pgeu-system, pglister) as an example, and moves the new site under "Community".More projects with more description and contact details should be added, of course. >> >> The purpose of this patch is to see if "Community" is the right place for this kind of information, and also what otherprojects and details should be included. > So, what is a project ? Useful extensions, local pg resources, > propaganda projects, educational sites, books, ... Extensions are already listed in the documentation and/or the PG Extension project (which by itself could be linked here). Books are also linked on the website. This is intended to bring more visibility to projects used and developed by the PostgreSQL project to help run things like infrastructure or conferences. There is quite a number of tools which are not visible otherwise. -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
On Sun, 2 Feb 2020, 15:26 Andreas 'ads' Scherbaum, <ads@pgug.de> wrote:
On 01/02/2020 20:30, Oleg Bartunov wrote:
> On Sat, Feb 1, 2020 at 1:51 AM Andreas 'ads' Scherbaum <ads@pgug.de> wrote:
>>
>> Hello,
>>
>> following a discussion how a number of not-so-known PostgreSQL projects can be made more visible, attached is a first draft to list them on the website.
>>
>> The draft lists three projects (pgweb, pgeu-system, pglister) as an example, and moves the new site under "Community". More projects with more description and contact details should be added, of course.
>>
>> The purpose of this patch is to see if "Community" is the right place for this kind of information, and also what other projects and details should be included.
> So, what is a project ? Useful extensions, local pg resources,
> propaganda projects, educational sites, books, ...
Extensions are already listed in the documentation and/or the PG Extension
project (which by itself could be linked here). Books are also linked on the
website. This is intended to bring more visibility to projects used and
developed
by the PostgreSQL project to help run things like infrastructure or
conferences. There is quite a number of tools which are not visible
otherwise.
Then, what is the purpose to make them visible ? They are internal projects not for regular users.
--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project
> This is intended to bring more visibility to projects used and > developed > by the PostgreSQL project to help run things like infrastructure or > conferences. There is quite a number of tools which are not visible > otherwise. > > Then, what is the purpose to make them visible ? They are internal projects not for regular users. I think the gist of this is that they very well may be for anyone, they are just quite unknown and dont reach a large audience as of now. The pgeu-system for example is used even outside of the postgres community these days. The question of what an auxiliary project is, and whick ones qualify, should probably be clarified somewhere however. cheers ./daniel
On 02/02/2020 17:52, Daniel Gustafsson wrote: >> This is intended to bring more visibility to projects used and >> developed >> by the PostgreSQL project to help run things like infrastructure or >> conferences. There is quite a number of tools which are not visible >> otherwise. >> >> Then, what is the purpose to make them visible ? They are internal projects not for regular users. > I think the gist of this is that they very well may be for anyone, they are > just quite unknown and dont reach a large audience as of now. The pgeu-system > for example is used even outside of the postgres community these days. Indeed. It's not about keeping this software under the shelf, but about a) making it visible, b) enable other people to use it and c) potentially have other people contribute to it. All of this doesn't work if it's hidden in a repo on git.postgresql.org. That's why I initially did not only add the project itself, but also contact information. > The question of what an auxiliary project is, and whick ones qualify, should > probably be clarified somewhere however. Open to suggestions. Also to what other projects should be included. -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
On 01/02/2020 01:31, Jonathan S. Katz wrote: > On 1/31/20 7:24 PM, Andreas 'ads' Scherbaum wrote: >> On 01/02/2020 00:37, Jonathan S. Katz wrote: >>> On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >>>> Hello, >>>> >>>> following a discussion how a number of not-so-known PostgreSQL projects >>>> can be made more visible, attached is a first draft to list them on the >>>> website. >>>> >>>> The draft lists three projects (pgweb, pgeu-system, pglister) as an >>>> example, and moves the new site under "Community". More projects with >>>> more description and contact details should be added, of course. >>> Seems like a good way to get people more involved. >>> >>>> The purpose of this patch is to see if "Community" is the right place >>>> for this kind of information, and also what other projects and details >>>> should be included. >>> Are there any HTML templates? I only see the URL added in the context. >> Actually, you are right. And the second part in my initial email just >> repeated the "contexts.py" file, instead of adding the correct file. >> Attached a new patch. > OK, that makes much more sense ;) > > Feedback / bikeshedding: > > - I'd recommend putting the pith of the content in a subsection under > "Developers". I don't see any issue linking to it from the community > section (and perhaps rewriting the community page a bit to link to more > of the "contributing areas", but the page is more about ways you can > develop around things in PostgreSQL > > - I'm not sure how I feel about the term "Auxiliary" - it's not used so > much any more and definitely prone to misspellings. Perhaps "Related > Projects"? > > - I like the overall layout of the page and how there is content around > each project. I think it's a good start. I moved the website over from "community" to "development", and renamed it. I also added a couple more projects, but ideas are still welcome. Patch attached. -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
Attachment
On 23/02/2020 02:23, Andreas 'ads' Scherbaum wrote: > On 01/02/2020 01:31, Jonathan S. Katz wrote: >> On 1/31/20 7:24 PM, Andreas 'ads' Scherbaum wrote: >>> On 01/02/2020 00:37, Jonathan S. Katz wrote: >>>> On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >>>>> Hello, >>>>> >>>>> following a discussion how a number of not-so-known PostgreSQL >>>>> projects >>>>> can be made more visible, attached is a first draft to list them >>>>> on the >>>>> website. >>>>> >>>>> The draft lists three projects (pgweb, pgeu-system, pglister) as an >>>>> example, and moves the new site under "Community". More projects with >>>>> more description and contact details should be added, of course. >>>> Seems like a good way to get people more involved. >>>> >>>>> The purpose of this patch is to see if "Community" is the right place >>>>> for this kind of information, and also what other projects and >>>>> details >>>>> should be included. >>>> Are there any HTML templates? I only see the URL added in the context. >>> Actually, you are right. And the second part in my initial email just >>> repeated the "contexts.py" file, instead of adding the correct file. >>> Attached a new patch. >> OK, that makes much more sense ;) >> >> Feedback / bikeshedding: >> >> - I'd recommend putting the pith of the content in a subsection under >> "Developers". I don't see any issue linking to it from the community >> section (and perhaps rewriting the community page a bit to link to more >> of the "contributing areas", but the page is more about ways you can >> develop around things in PostgreSQL >> >> - I'm not sure how I feel about the term "Auxiliary" - it's not used so >> much any more and definitely prone to misspellings. Perhaps "Related >> Projects"? >> >> - I like the overall layout of the page and how there is content around >> each project. I think it's a good start. > > I moved the website over from "community" to "development", and > renamed it. > > I also added a couple more projects, but ideas are still welcome. While working on GSoC projects, I found a couple more candidates for this website. New patch attached, still applies clean on pgweb. Regards, -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
Attachment
On 3/28/20 1:30 AM, Andreas 'ads' Scherbaum wrote: > On 23/02/2020 02:23, Andreas 'ads' Scherbaum wrote: >> On 01/02/2020 01:31, Jonathan S. Katz wrote: >>> On 1/31/20 7:24 PM, Andreas 'ads' Scherbaum wrote: >>>> On 01/02/2020 00:37, Jonathan S. Katz wrote: >>>>> On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >>>>>> Hello, >>>>>> >>>>>> following a discussion how a number of not-so-known PostgreSQL >>>>>> projects >>>>>> can be made more visible, attached is a first draft to list them >>>>>> on the >>>>>> website. >>>>>> >>>>>> The draft lists three projects (pgweb, pgeu-system, pglister) as an >>>>>> example, and moves the new site under "Community". More projects with >>>>>> more description and contact details should be added, of course. >>>>> Seems like a good way to get people more involved. >>>>> >>>>>> The purpose of this patch is to see if "Community" is the right place >>>>>> for this kind of information, and also what other projects and >>>>>> details >>>>>> should be included. >>>>> Are there any HTML templates? I only see the URL added in the context. >>>> Actually, you are right. And the second part in my initial email just >>>> repeated the "contexts.py" file, instead of adding the correct file. >>>> Attached a new patch. >>> OK, that makes much more sense ;) >>> >>> Feedback / bikeshedding: >>> >>> - I'd recommend putting the pith of the content in a subsection under >>> "Developers". I don't see any issue linking to it from the community >>> section (and perhaps rewriting the community page a bit to link to more >>> of the "contributing areas", but the page is more about ways you can >>> develop around things in PostgreSQL >>> >>> - I'm not sure how I feel about the term "Auxiliary" - it's not used so >>> much any more and definitely prone to misspellings. Perhaps "Related >>> Projects"? >>> >>> - I like the overall layout of the page and how there is content around >>> each project. I think it's a good start. >> >> I moved the website over from "community" to "development", and >> renamed it. >> >> I also added a couple more projects, but ideas are still welcome. > > While working on GSoC projects, I found a couple more candidates > for this website. New patch attached, still applies clean on pgweb. looking at this I'm not sure why you added the lcov/code coverage to the list - I find that going way to far in terms of what "the community" uses, if we really go that far we need to add a ton of more or less random pieces of software(homegrown or not). Stefan
On 29/03/2020 14:35, Stefan Kaltenbrunner wrote: > On 3/28/20 1:30 AM, Andreas 'ads' Scherbaum wrote: >> On 23/02/2020 02:23, Andreas 'ads' Scherbaum wrote: >>> On 01/02/2020 01:31, Jonathan S. Katz wrote: >>>> On 1/31/20 7:24 PM, Andreas 'ads' Scherbaum wrote: >>>>> On 01/02/2020 00:37, Jonathan S. Katz wrote: >>>>>> On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >>>>>>> Hello, >>>>>>> >>>>>>> following a discussion how a number of not-so-known PostgreSQL >>>>>>> projects >>>>>>> can be made more visible, attached is a first draft to list them >>>>>>> on the >>>>>>> website. >>>>>>> >>>>>>> The draft lists three projects (pgweb, pgeu-system, pglister) as an >>>>>>> example, and moves the new site under "Community". More projects with >>>>>>> more description and contact details should be added, of course. >>>>>> Seems like a good way to get people more involved. >>>>>> >>>>>>> The purpose of this patch is to see if "Community" is the right place >>>>>>> for this kind of information, and also what other projects and >>>>>>> details >>>>>>> should be included. >>>>>> Are there any HTML templates? I only see the URL added in the context. >>>>> Actually, you are right. And the second part in my initial email just >>>>> repeated the "contexts.py" file, instead of adding the correct file. >>>>> Attached a new patch. >>>> OK, that makes much more sense ;) >>>> >>>> Feedback / bikeshedding: >>>> >>>> - I'd recommend putting the pith of the content in a subsection under >>>> "Developers". I don't see any issue linking to it from the community >>>> section (and perhaps rewriting the community page a bit to link to more >>>> of the "contributing areas", but the page is more about ways you can >>>> develop around things in PostgreSQL >>>> >>>> - I'm not sure how I feel about the term "Auxiliary" - it's not used so >>>> much any more and definitely prone to misspellings. Perhaps "Related >>>> Projects"? >>>> >>>> - I like the overall layout of the page and how there is content around >>>> each project. I think it's a good start. >>> I moved the website over from "community" to "development", and >>> renamed it. >>> >>> I also added a couple more projects, but ideas are still welcome. >> While working on GSoC projects, I found a couple more candidates >> for this website. New patch attached, still applies clean on pgweb. > looking at this I'm not sure why you added the lcov/code coverage to the > list - I find that going way to far in terms of what "the community" > uses, if we really go that far we need to add a ton of more or less > random pieces of software(homegrown or not). Reason was that I went to the main website and checked the projects I found there. But your explanation makes sense, and I removed it. All the other listed projects are PG-related. New patch attached. Regards, -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
Attachment
On 4/9/20 6:59 PM, Andreas 'ads' Scherbaum wrote: > On 29/03/2020 14:35, Stefan Kaltenbrunner wrote: >> On 3/28/20 1:30 AM, Andreas 'ads' Scherbaum wrote: >>> On 23/02/2020 02:23, Andreas 'ads' Scherbaum wrote: >>>> On 01/02/2020 01:31, Jonathan S. Katz wrote: >>>>> On 1/31/20 7:24 PM, Andreas 'ads' Scherbaum wrote: >>>>>> On 01/02/2020 00:37, Jonathan S. Katz wrote: >>>>>>> On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> following a discussion how a number of not-so-known PostgreSQL >>>>>>>> projects >>>>>>>> can be made more visible, attached is a first draft to list them >>>>>>>> on the >>>>>>>> website. >>>>>>>> >>>>>>>> The draft lists three projects (pgweb, pgeu-system, pglister) as an >>>>>>>> example, and moves the new site under "Community". More projects >>>>>>>> with >>>>>>>> more description and contact details should be added, of course. >>>>>>> Seems like a good way to get people more involved. >>>>>>> >>>>>>>> The purpose of this patch is to see if "Community" is the right >>>>>>>> place >>>>>>>> for this kind of information, and also what other projects and >>>>>>>> details >>>>>>>> should be included. >>>>>>> Are there any HTML templates? I only see the URL added in the >>>>>>> context. >>>>>> Actually, you are right. And the second part in my initial email just >>>>>> repeated the "contexts.py" file, instead of adding the correct file. >>>>>> Attached a new patch. >>>>> OK, that makes much more sense ;) >>>>> >>>>> Feedback / bikeshedding: >>>>> >>>>> - I'd recommend putting the pith of the content in a subsection under >>>>> "Developers". I don't see any issue linking to it from the community >>>>> section (and perhaps rewriting the community page a bit to link to >>>>> more >>>>> of the "contributing areas", but the page is more about ways you can >>>>> develop around things in PostgreSQL >>>>> >>>>> - I'm not sure how I feel about the term "Auxiliary" - it's not >>>>> used so >>>>> much any more and definitely prone to misspellings. Perhaps "Related >>>>> Projects"? >>>>> >>>>> - I like the overall layout of the page and how there is content >>>>> around >>>>> each project. I think it's a good start. >>>> I moved the website over from "community" to "development", and >>>> renamed it. >>>> >>>> I also added a couple more projects, but ideas are still welcome. >>> While working on GSoC projects, I found a couple more candidates >>> for this website. New patch attached, still applies clean on pgweb. >> looking at this I'm not sure why you added the lcov/code coverage to the >> list - I find that going way to far in terms of what "the community" >> uses, if we really go that far we need to add a ton of more or less >> random pieces of software(homegrown or not). > > Reason was that I went to the main website and checked the projects > I found there. But your explanation makes sense, and I removed it. > All the other listed projects are PG-related. > > > New patch attached. Attached is another revision. I fixed up the HTML formatting and added to and reworded several sections, as well as changed the URL. If you believe this patch captures the spirit of what you are trying to accomplish, I am happy to commit it. Thanks, Jonathan
Attachment
On 10/04/2020 02:36, Jonathan S. Katz wrote: > On 4/9/20 6:59 PM, Andreas 'ads' Scherbaum wrote: >> On 29/03/2020 14:35, Stefan Kaltenbrunner wrote: >>> On 3/28/20 1:30 AM, Andreas 'ads' Scherbaum wrote: >>>> On 23/02/2020 02:23, Andreas 'ads' Scherbaum wrote: >>>>> On 01/02/2020 01:31, Jonathan S. Katz wrote: >>>>>> On 1/31/20 7:24 PM, Andreas 'ads' Scherbaum wrote: >>>>>>> On 01/02/2020 00:37, Jonathan S. Katz wrote: >>>>>>>> On 1/31/20 5:50 PM, Andreas 'ads' Scherbaum wrote: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> following a discussion how a number of not-so-known PostgreSQL >>>>>>>>> projects >>>>>>>>> can be made more visible, attached is a first draft to list them >>>>>>>>> on the >>>>>>>>> website. >>>>>>>>> >>>>>>>>> The draft lists three projects (pgweb, pgeu-system, pglister) as an >>>>>>>>> example, and moves the new site under "Community". More projects >>>>>>>>> with >>>>>>>>> more description and contact details should be added, of course. >>>>>>>> Seems like a good way to get people more involved. >>>>>>>> >>>>>>>>> The purpose of this patch is to see if "Community" is the right >>>>>>>>> place >>>>>>>>> for this kind of information, and also what other projects and >>>>>>>>> details >>>>>>>>> should be included. >>>>>>>> Are there any HTML templates? I only see the URL added in the >>>>>>>> context. >>>>>>> Actually, you are right. And the second part in my initial email just >>>>>>> repeated the "contexts.py" file, instead of adding the correct file. >>>>>>> Attached a new patch. >>>>>> OK, that makes much more sense ;) >>>>>> >>>>>> Feedback / bikeshedding: >>>>>> >>>>>> - I'd recommend putting the pith of the content in a subsection under >>>>>> "Developers". I don't see any issue linking to it from the community >>>>>> section (and perhaps rewriting the community page a bit to link to >>>>>> more >>>>>> of the "contributing areas", but the page is more about ways you can >>>>>> develop around things in PostgreSQL >>>>>> >>>>>> - I'm not sure how I feel about the term "Auxiliary" - it's not >>>>>> used so >>>>>> much any more and definitely prone to misspellings. Perhaps "Related >>>>>> Projects"? >>>>>> >>>>>> - I like the overall layout of the page and how there is content >>>>>> around >>>>>> each project. I think it's a good start. >>>>> I moved the website over from "community" to "development", and >>>>> renamed it. >>>>> >>>>> I also added a couple more projects, but ideas are still welcome. >>>> While working on GSoC projects, I found a couple more candidates >>>> for this website. New patch attached, still applies clean on pgweb. >>> looking at this I'm not sure why you added the lcov/code coverage to the >>> list - I find that going way to far in terms of what "the community" >>> uses, if we really go that far we need to add a ton of more or less >>> random pieces of software(homegrown or not). >> Reason was that I went to the main website and checked the projects >> I found there. But your explanation makes sense, and I removed it. >> All the other listed projects are PG-related. >> >> >> New patch attached. > Attached is another revision. I fixed up the HTML formatting and added > to and reworded several sections, as well as changed the URL. > > If you believe this patch captures the spirit of what you are trying to > accomplish, I am happy to commit it. Oh yes, that looks very good! Thanks for spending the time! Did review it, didn't spot anything out of place. Ok for commit from my side. Regards, -- Andreas 'ads' Scherbaum German PostgreSQL User Group European PostgreSQL User Group - Board of Directors Volunteer Regional Contact, Germany - PostgreSQL Project
On 4/10/20 7:39 AM, Andreas 'ads' Scherbaum wrote: > On 10/04/2020 02:36, Jonathan S. Katz wrote: >> Attached is another revision. I fixed up the HTML formatting and added >> to and reworded several sections, as well as changed the URL. >> >> If you believe this patch captures the spirit of what you are trying to >> accomplish, I am happy to commit it. > > Oh yes, that looks very good! Thanks for spending the time! > > Did review it, didn't spot anything out of place. > Ok for commit from my side. Thanks! I added "Planet PostgreSQL" to the list and pushed it. Thanks for pulling this together. Jonathan