>
> If I fork it, I'll have to change the library name, and that will make me
> incompatible with the rest of the world--all downstream consumers including
> my own.
^ Is an assumption.
You could start with the fork on GitHub 'as is' and make one tiny addition
to the resulting linkable object. S
GitHub heralded one fantastic thing that didn't exist before - easy forking
or a repo. That is more likely to force an 'upstream' dev team to be more
benevolent to directions of others. Perhaps because of the possibility of
mind-share shifting to the fork and away from the upstream/origin. That
div
pull requests). You don't want to donate something to a
team that can't consume reasonably quickly.
- Paul
On Sat, Feb 3, 2018 at 11:03 PM, Thaddeus Brown
wrote:
> I would like to know how I could become a member or show a contribution?
>
--
Paul Hammant DevOps <https:
Say to unsubscribe from THIS email list
1. send an email to dev-unsubscr...@community.apache.org
2. follow the instructions from the auto-response you get back.
It is the -unsubscribe piece you need to add to the email address that
starts the unsubscribe workflow for you.
-ph
[Nicolas Fränkel posted the link to proggit today]
There are two initiatives that spring to mind (and I'm sure I've come
across more, but can't recall them right now).
1. Make a README - https://www.makeareadme.com/
2. Keep A Changelog - http://keepachangelog.com/
*I have a feeling there are thi
Just double checking before posting, something longer.
According to this page -
https://community.apache.org/apache-way/apache-project-maturity-model.html
- questions & feedback for the "Apache project maturity model" are made
here on dev@community.apache.org.
Is that correct?
- Paul
