Re: [OSGeo-Discuss] Introduction

2019-10-18 Thread Pierre Abbat
On Friday, 18 October 2019 14.11.26 EDT Cameron Shorter wrote:
> Hi Pierre,
> 
> Welcome to the OSGeo community. It sounds like you have grit and
> tenacity if you have been sticking with a project for 11 years. They are
> valuable qualities in an open source developer.
> 
> I'll give you some tough advice which you possibly were not looking for.
> (You'd really want to get some co-contributors, right?)
> 
> Most Open Source projects fail.
> http://cameronshorter.blogspot.com/2018/11/comprehensive-research-into-open-> 
> source.html
> 
> One of the key criteria for long term success is to attract community. I
> feel it is much better to start with a community and then build
> software, rather than start with software and then attract community.
> 
> With open source software, it is best to use, extend, create (in that
> order).
> 
> I'd suggest look at existing OSGeo projects. Do any do what you do? If
> so, then join that project and that community. If something is close,
> then join the community and offer to add your extra functionality into
> their codebase. (I know, it will be harder than doing it yourself, but
> the advantage is that you will get a community.)
> 
> In looking for established projects, check out:
> https://live.osgeo.org/en/metrics.html (and pay more attention to the
> projects which have a strong community.)
> 
> Good luck.

I'm thinking that PerfectTIN would be easier to attract contributors to. It's 
taken me less than a year to make something useful, and it does one main 
thing, convert point clouds to TINs. Source code is about 1/4 the size of 
Bezitopo. Once someone has understood PerfectTIN well enough to contribute, 
Bezitopo won't be too hard, as much of the code is the same.

I'll answer the other message (which was sent off-list) another day. The work 
week ends in ten minutes, I just got back from continuing education, and I 
need to sleep.

Pierre
-- 
Jews use a lunisolar calendar; Muslims use a solely lunar calendar.



___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] Introduction

2019-10-18 Thread Cameron Shorter

Hi Pierre,

Welcome to the OSGeo community. It sounds like you have grit and 
tenacity if you have been sticking with a project for 11 years. They are 
valuable qualities in an open source developer.


I'll give you some tough advice which you possibly were not looking for. 
(You'd really want to get some co-contributors, right?)


Most Open Source projects fail. 
http://cameronshorter.blogspot.com/2018/11/comprehensive-research-into-open-source.html


One of the key criteria for long term success is to attract community. I 
feel it is much better to start with a community and then build 
software, rather than start with software and then attract community.


With open source software, it is best to use, extend, create (in that 
order).


I'd suggest look at existing OSGeo projects. Do any do what you do? If 
so, then join that project and that community. If something is close, 
then join the community and offer to add your extra functionality into 
their codebase. (I know, it will be harder than doing it yourself, but 
the advantage is that you will get a community.)


In looking for established projects, check out: 
https://live.osgeo.org/en/metrics.html (and pay more attention to the 
projects which have a strong community.)


Good luck.

On 16/10/19 8:07 pm, Pierre Abbat wrote:

I found OsGeo while looking for software to turn a ZHD or GNS file into a
RINEX file that I could run on my Linux laptop.

I am a North Carolina land surveyor who have been working on a land surveying
CAD program for over eleven years, starting when I was in surveying school.
It's been on GitHub for years, but I'm still the only developer. I've also
started some point cloud processing software, but it's not public yet.

What I'd like to find is:
*Other people interested in contributing. The programs are written in C++, but
there are things to do that don't involve coding, such as writing help files,
entering map projection data, drawing button icons, and translating.
*A source of funding. I have a lead of a possible job, but it may be a few
weeks before I hear back. I'm not in danger of running out of money, but I
would like to buy some computers to test software on more OSes and processors.
*Ideas on how to package and sell software. It's free software, but most
surveyors I know run Windows, not Linux or BSD, and don't know how to install
software from source. I've gotten it to run on Windows, but still haven't
figured out how to package it. I'm thinking I could sell CDs with Windows
binaries and source code.
*Other projects that I might could contribute to.

The CAD program is at http://bezitopo.org/ and in the Git repo at https://
github.com/phma/bezitopo .

Pierre


--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant

M +61 (0) 419 142 254

___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] [OSGeo-Standards] [Board] glossary discussion on osgeo-standards ....

2019-10-18 Thread Angelos Tzotsos

Hi,

In that case we should probably arrange a specific call for this topic.
I think the only working timeslot would be around 20:00-22:00 UTC

On 10/17/19 9:24 PM, Cameron Shorter wrote:
Angelos, the board meeting is 3am for me. The 3 of us involved are in 
this Asian/Australia timezone.


Reese, we can get you set up with IRC (Internet Chat Relay) quite 
easily. It is text based only. Quickest way to get started is with the 
web client: https://webchat.freenode.net/


On 17/10/19 10:19 pm, rpl...@tc211tmg.org wrote:
hello Angelos, thank you for the invitation, two issues for me, local 
time is 1am and i have never done Internet Relay Chat. i can do skype 
or zoom. if you have another time/date let me know.  sorry about this 
time.

reese


    - Original Message -
    From:
    "Angelos Tzotsos" 

    To:
    "Cameron Shorter" ,
    , "bo...@lists.osgeo.org"
    , "OSGeo Discussions" 


    Cc:
    "Reese Plews" 
    Sent:
    Thu, 17 Oct 2019 12:14:37 +0300
    Subject:
    Re: [OSGeo-Standards] [Board] glossary discussion on
    osgeo-standards 


    Hi all,

    Would someone be available to join our next board meeting to
    discuss this issue?
    https://wiki.osgeo.org/wiki/Board_Meeting_2019-10-28

    Regards,
    Angelos

    On 10/15/19 9:52 PM, Cameron Shorter wrote:

    OSGeo Board, OSGeo Discuss,

    I'd like to introduce you to this proposal that Ron and Reese
    have been developing on the OSGeo Standards email list, which
    I think should fit under the legal structure of an OSGeo
    Committee.

    I have vague recollections that setting up a committee
    requires board approval? I've found some old tips on running a
    committee here: https://wiki.osgeo.org/wiki/Committee_Guidelines

    Comments welcomed.

    On 15/10/19 4:47 pm, Ronald Tse wrote:

    Hi Cameron,

    Thank you for the suggestions! I have updated the proposal
    to reflect your comments below.

    I would be honored to help with terminology management at
    OSGeo. Can’t speak for Reese but with his leadership in
    already doing terminology cleanup on Felicity’s sheet, he
    seems pretty committed already :-)

    Ron

    ———

    Recommendations for OSGeo terminology management

    1. Establish a terminology management group in OSGeo.

    ISO/TC 211, IEC Electropedia and OGC all have one for
    terminology management. The existence of this group is
    crucial to the success of the OSGeo terminology database.
    It will play two essential roles:

    a) As the gatekeeper of terms to ensure quality checks of
    contributions
    b) As the seat of central terminology knowledge for
    alignment of terms and concepts. To facilitate the flow of
    terminology knowledge to terminology authors and users.

    It would be helpful to involve representation from ISO/TC
    211 and OGC in this group, in order to leverage their
    experience in terminology. Such experience will be useful
    in situations such as alerting on cross-organization
    alignment of concepts or term duplication.

    An email list shall be setup for this group for internal
    communication.


    2. Establish a terms of reference for terminology 
management.


    For the terminology management group, a terms of reference
    should be produced so that the steps for approval and data
    quality requirements are clear. This should be openly
    shared with contributors so they are clear on acceptance
    criteria.

    Contributors may propose changes to the terminology
    database at any time. The terminology management group
    shall discuss and approve or disapprove of the proposal
    within a reasonable timeframe. This practice is in-line
    with the open source, change-based, rapid iteration
    mantra, similar to OpenSSL.

    For releases, the group shall convene periodically, such
    as every 4-6 months, to discuss previously decided
    proposals, governance or technical issues related to
    terminology management.

    The method of submitting change requests shall also be
    determined and announced so that contributors understand
    the necessary processes and timeline.


    3. Establish an online terminology database presence.

    Terminology isn’t useful until people use them, which
    means people need to first know they exist and what they
    mean. Geolexica is an initiative that currently serves
    ISO/TC 211’s terminology management group in making its
    multi-lingual geographic information terminology available
    on the