[Incubator] Fwd: pycsw incubation application

[Angelos Tzotsos]

Hi Daniel,

I totally agree that in the Free Software world, community is the blood 
of each project.
We must have in mind that not all projects are/can be the size of GNU or 
Linux kernel though :)

On our side, we have managed to attract more devs in the last year and 
through our move from SVN to Git (and GitHub) we have attracted some 
more code contributions. We also have 15 people registered on our 
mailing list and (unfortunately?) most of the user reports and 
discussions are going through the IRC channel first, since we are 
available there most of the time. We are trying to tunnel some of those 
users in the mailing list to show more activity there.

Recently GeoNode made the decision to include pycsw as a default CSW 
server replacing GeoNetwork. We are expecting huge community push from 
this collaboration.
Same applies with our scheduled CKAN 2.0 integration (more details can 
be found on our mailing list posts). This is the #1 catalog solution for 
open data movement and we are committed to make this happen.

We are already getting traffic within the ckan-dev and geonode-dev 
mailing lists but this is normal for projects acting as standalone + 
embeddable library...

If the committee decides that we do not meet the incubation criteria or 
that we are not ready yet, we can revisit/reapply in 6-12 months time.

We are available to be present for the next committee meeting if you 
wish to discuss more about our application.

Best regards,
Angelos

On 12/18/2012 03:19 PM, Daniel Morissette wrote:
> Hi Angelos,
>
> Thank you for adding this Community page and link, it looks perfect to 
> me.
>
> I agree with Eli that it's hard to decide which pages are important 
> enough to make it to the nav. bar. when we design a website, but I 
> think that for an open source project, a link to something like this 
> community page is essential since the community is the blood of the 
> project: without a community of users and developers the project is 
> just stale source code. In the proprietary world there is a company 
> pumping blood into a product through its marketing and R&D teams, in 
> the open source world the community of users and devs *is* the blood.
>
> Only my opinion of course, all points of view are much welcome...
>
> Daniel
>
>
> On 12-12-18 7:18 AM, Angelos Tzotsos wrote:
>> Hi Daniel and Eli,
>>
>> Thanks for your feedback.
>> We have made some changes, adding a Community link on the first page.
>>
>> http://pycsw.org/
>> http://pycsw.org/community.html
>>
>> Comments and questions are welcome.
>>
>> Best regards,
>> Angelos
>>
>> On 12/14/2012 09:03 PM, Eli Adam wrote:
>>> On Fri, Dec 14, 2012 at 10:31 AM, Daniel Morissette
>>> <dmorissette at mapgears.com> wrote:
>>>> On 12-12-14 1:07 PM, Eli Adam wrote:
>>>>>
>>>>> I don't know if this is new since yesterday, but I did find,
>>>>> http://pycsw.org/docs/support.html?highlight=mail and
>>>>> http://pycsw.org/docs/development.html?highlight=mail neither of 
>>>>> which
>>>>> were very prominent to people making little effort to find it.  It is
>>>>> hard to decide which are the most prominent items to put on the home
>>>>> page.
>>>>>
>>>> That's probably not new, I just didn't find it, thank you for the
>>>> pointer.
>>>> Unfortunately the shortest path I can find to get to it is 3 levels 
>>>> down
>>>> from the home page:
>>>>
>>>>    Home -> Docs -> 1.4.0 -> (scroll-down) -> Support
>>>>
>>>> Now that I know what to look for I guess I could have used the search
>>>> box.
>>>>
>>>> This made me realize that this site structure seems to be inspired
>>>> from the
>>>> MapServer website which suffers from a similar problem (except that
>>>> MapServer has a link to the "community activities" page in the intro
>>>> text of
>>>> the home page, but it's still fairly easy to miss).
>>> Putting the 'most important' things in a 'most prominent' manner is
>>> always very difficult, well at least deciding what those things are
>>> can be difficult.
>>>
>>> It has been my opinion for many years that the best approach to the
>>> MapServer documentation (which I think is great) is to use the search.
>>>   The same is probably true for GeoMOOSE and pycsw (and other Sphinx
>>> based) documentation.
>>>
>>> Eli
>>>
>>>>
>>>> -- 
>>>> Daniel Morissette
>>>> http://www.mapgears.com/
>>>> Provider of Professional MapServer Support since 2000
>>>>
>>>> _______________________________________________
>>>> Incubator mailing list
>>>> Incubator at lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/incubator
>>> _______________________________________________
>>> Incubator mailing list
>>> Incubator at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/incubator
>>>
>>
>>
>
>


-- 
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
http://users.ntua.gr/tzotsos