Sorry, last message got away from me. The point of the use cases is to get
a rough consensus of the kinds of things that a Sharpener will work on.
Ideally, these get a) fixed / better organized and b) fleshed out with
useful links, suggestions and scope of engagement statements.
So for example,
OK, I added a brain dump on the use cases. This is in the spirit of "good
ideas, bad code" ;)
Phil
On Mon, Feb 12, 2024 at 2:06 PM Phil Steitz wrote:
> I just added a patch to the readme and to add me to the members list.
> Perfectly OK if the patch is rejected. I can see both sides of this.
[
https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated COMDEV-543:
---
Attachment: use-cases.md
> Sharpeniers use cases
> -
>
> Key:
[
https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated COMDEV-543:
---
Summary: Sharpeners use cases (was: Sharpeniers use cases)
> Sharpeners use cases
>
[
https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated COMDEV-543:
---
Priority: Minor (was: Major)
> Sharpeniers use cases
> -
>
>
Phil Steitz created COMDEV-543:
--
Summary: Sharpeniers use cases
Key: COMDEV-543
URL: https://issues.apache.org/jira/browse/COMDEV-543
Project: Community Development
Issue Type: Improvement
I just added a patch to the readme and to add me to the members list.
Perfectly OK if the patch is rejected. I can see both sides of this. I
just want to be very careful not to encourage too much private discussion
and "community adjustment" happening without visibility or input of
community
[
https://issues.apache.org/jira/browse/COMDEV-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated COMDEV-542:
---
Attachment: sharpeners.patch
> More public tone for sharpeners
> ---
>
>
Phil Steitz created COMDEV-542:
--
Summary: More public tone for sharpeners
Key: COMDEV-542
URL: https://issues.apache.org/jira/browse/COMDEV-542
Project: Community Development
Issue Type:
> On Feb 11, 2024, at 6:24 AM, Slawomir Jaranowski
> wrote:
>
> Hi,
>
> Thanks for the idea ...
>
> Some time ago we discuss on Maven slack channel who can publish message
> behalf of ASF like announcements about new releases
>
> Clear rules for ASF wide and for project accounts will be
> On Feb 12, 2024, at 10:24 AM, sebb wrote:
>
> Why not migrate the SVN repo to Git?
> Is there any need to keep the info in SVN?
FWIW, I have no opinion on this, beyond my fiery and abiding antipathy for Git.
If that’s what people want, go ahead, and I’ll adjust. This is a discussion.
I’m
> On Feb 12, 2024, at 10:57 AM, tison wrote:
>
> Thank you for starting this discussion, Rich.
>
> I'm trying to get the points of this WG:
>
> 1. This WG is NOT a new office to "shepherd" TLPs, but to write down
> how any community member can help in sharpening an ASF project.
> 2. For
> On Feb 12, 2024, at 10:46 AM, tison wrote:
>
>> Why not migrate the SVN repo to Git?
>> Is there any need to keep the info in SVN?
>
> I'm +1 in this direction. But it doesn't bother me if we keep a gate
> to allow commiting via SVN and sync to GitHub. If Rich likes this way
> and now he is
Thank you for starting this discussion, Rich.
I'm trying to get the points of this WG:
1. This WG is NOT a new office to "shepherd" TLPs, but to write down
how any community member can help in sharpening an ASF project.
2. For applying any suggestions, the request is delegated to the
Board,
> Why not migrate the SVN repo to Git?
> Is there any need to keep the info in SVN?
I'm +1 in this direction. But it doesn't bother me if we keep a gate
to allow commiting via SVN and sync to GitHub. If Rich likes this way
and now he is the most active volunteer on this initiative.
Best,
tison.
Why not migrate the SVN repo to Git?
Is there any need to keep the info in SVN?
On Mon, 12 Feb 2024 at 15:14, tison wrote:
>
> According to the INFRA ticket [1], we'd better create the
> apache/community GitHub repo first.
>
> I'm glad to execute the self-serve command but I'm yet to be a COMDEV
On Feb 12, 2024, at 10:13 AM, tison wrote:
>
> According to the INFRA ticket [1], we'd better create the
> apache/community GitHub repo first.
>
> I'm glad to execute the self-serve command but I'm yet to be a COMDEV
> PMC member. I remember that in another thread, it's said that an
> Apache
—
Rich Bowen
rbo...@rcbowen.com
> On Feb 11, 2024, at 6:04 PM, Phil Steitz wrote:
>
> I am working on a PR to take a stab at tweaking the wording. I am also
> playing with some ideas around use cases - kinds of things sharpeners will
> work on. I think it's really a good idea to get some
According to the INFRA ticket [1], we'd better create the
apache/community GitHub repo first.
I'm glad to execute the self-serve command but I'm yet to be a COMDEV
PMC member. I remember that in another thread, it's said that an
Apache Member can self-request to be a PMC member, so:
* If any
Hi, Ayaan,
Thanks for your interest in the Apache Software Foundation.
New projects enter the ASF through the Incubator, which you can read about at
https://incubator.apache.org/
In particular, this document - https://incubator.apache.org/cookbook/ - may
help you decide whether the ASF is a
20 matches
Mail list logo
