You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Elliotte Rusty Harold <el...@ibiblio.org> on 2023/04/21 11:21:47 UTC
The Curse of Knowledge as applied to open source projects
This article about Qt is worth a read:
https://kelteseth.com/post/20-04-2023-current-issues-with-the-qt-project-from-the-outside-looking-in/
Parts of this will sound very familiar to anyone who's tried to
contribute to Xalan, or indeed most Apache projects. While some of the
issues Qt has involve being maintained by a for-profit company, the
rest of it is quite applicable. The more idiosyncratic a development
process is, the more likely potential contributors are to bounce off
the project and look elsewhere.
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: The Curse of Knowledge as applied to open source projects
Posted by Joseph Kesselman <ke...@alum.mit.edu>.
All of which sounds reasonable to me, unless Apache has a reason for maintaining it's own git other than "that's how we started".
Still waiting for permissions to come through, but I could start reviewing old branches to see if they were already merged or otherwise addressed...
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!
________________________________
From: Elliotte Rusty Harold <el...@ibiblio.org>
Sent: Friday, April 21, 2023, 12:13 PM
To: dev@xalan.apache.org <de...@xalan.apache.org>
Subject: Re: The Curse of Knowledge as applied to open source projects
On Fri, Apr 21, 2023 at 7:53 AM Joseph Kesselman <ke...@alum.mit.edu> wrote:
> The question is, what are folks finding most confusing/difficult, and is it something we can fix? Open Jira items for that, size, and prioritize appropriately?
1. Publish the release to Maven Central.
2. Make the main branch of Github the source of truth. Use Github for
all PRs and code reviews.
2a. No long lived branches. All development on the main branch that is
ready for release at any time.
3. Merge the tests into the primary Github repo on the main branch
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: The Curse of Knowledge as applied to open source projects
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
On Fri, Apr 21, 2023 at 7:53 AM Joseph Kesselman <ke...@alum.mit.edu> wrote:
> The question is, what are folks finding most confusing/difficult, and is it something we can fix? Open Jira items for that, size, and prioritize appropriately?
1. Publish the release to Maven Central.
2. Make the main branch of Github the source of truth. Use Github for
all PRs and code reviews.
2a. No long lived branches. All development on the main branch that is
ready for release at any time.
3. Merge the tests into the primary Github repo on the main branch
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: The Curse of Knowledge as applied to open source projects
Posted by Joseph Kesselman <ke...@alum.mit.edu>.
Elliotte Rusty Harold Friday, April 21, 7:23 AM
The more idiosyncratic a development<br>process is, the more likely potential contributors are to bounce off<br>the project and look elsewhere.
True enough. Though good documentation can make up for some of that.
The question is, what are folks finding most confusing/difficult, and is it something we can fix? Open Jira items for that, size, and prioritize appropriately?
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!
________________________________
From: Elliotte Rusty Harold <el...@ibiblio.org>
Sent: Friday, April 21, 2023 7:21:47 AM
To: dev@xalan.apache.org <de...@xalan.apache.org>
Subject: The Curse of Knowledge as applied to open source projects
This article about Qt is worth a read:
https://kelteseth.com/post/20-04-2023-current-issues-with-the-qt-project-from-the-outside-looking-in/
Parts of this will sound very familiar to anyone who's tried to
contribute to Xalan, or indeed most Apache projects. While some of the
issues Qt has involve being maintained by a for-profit company, the
rest of it is quite applicable. The more idiosyncratic a development
process is, the more likely potential contributors are to bounce off
the project and look elsewhere.
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org