Re: Access to Incubator Wiki - Submission of Podling report - Apache Training

[Justin Mclean]

Hi,

Only PPMC members can edit those pages.

Kind Regards,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-278) Outdated link to Apachecon 2022 on website

[Sebb (Jira)]

Sebb created INCUBATOR-278:
--

 Summary: Outdated link to Apachecon 2022 on website
 Key: INCUBATOR-278
 URL: https://issues.apache.org/jira/browse/INCUBATOR-278
 Project: Incubator
  Issue Type: Bug
Reporter: Sebb


The Incubator home page has a prominent link to

[https://www.apachecon.com/acna2022/]

 

This is very out of date.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Access to Incubator Wiki - Submission of Podling report - Apache Training

[PJ Fanning]

The cwiki Confluence instance requires your Apache username and
password. If you login with those credentials and you still can't edit
the page, you should check what your setup is in the whimsy tool[1].

[1] https://whimsy.apache.org

On Wed, 5 Jul 2023 at 19:34, Lars Francke  wrote:
>
> Hi Mirko,
>
> I'm afraid I can't remember the procedure to get access to that Wiki
> but I will read it now and move it there!
>
> Thank you very much.
>
> Cheers,
> Lars
>
> On Wed, Jul 5, 2023 at 2:25 PM Mirko Kämpf  wrote:
> >
> > Hello,
> >
> > I intend to submit the draft of the podling report to this page:
> > *https://cwiki.apache.org/confluence/display/incubator/July2023#training
> > *
> >
> > But unfortunately, I still have no write permission to this wiki.
> > My username is: mirko.kae...@gmail.com
> >
> >
> > Here is the draft in the *Apache Training Wiki:*
> > https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#PodlingReports-July2023
> > 
> >
> > And at the end of this mail is the full text of the draft.
> >
> > It has been shared on the project's developer list.
> > No comments so far.
> >
> > Cheers,
> > Mirko
> >
> >
> >
> >
> >
> > July 2023
> >
> > *Training
> > *
> >
> > The Training project aims to develop resources which can be used for
> > training purposes in various media formats, languages and for various
> > Apache and non-Apache target projects.
> >
> > Training has been incubating since 2019-02-21.
> >
> > In June, we started adjusting the project goals. Besides a pure focus on
> > content creation tools we have identified the need for two additional
> > aspects:
> > (1) For ASF processes some documentation exists, e.g.
> > https://community.apache.org/contributor-ladder, but the ASF member journey
> > is still a challenge for many new members, especially those with less
> > coding experience.
> > As a solution it has been suggested to provide training material for the
> > following problems:
> > * You've just graduated to a TLP. What are the challenges you will now face?
> > * New committer onboarding
> > * New PMC member onboarding
> > * New PMC Chair onboarding
> > * New board member onboarding
> >
> > (2) Creation of some general recommendations/guidelines for:
> >  * managing/validation of training material contributions of arbitrary ASF
> > projects
> > has been propsed.
> >
> > Initial discussion of the topics have been started.
> >
> > *We expand our focus now on the following aspects:*
> >
> > *We have to work on strategies to increase the** participation and the
> > visibility of the project and its goals.*
> >
> > *Besides requests** for contributions from individual contributors** from
> > other Apache projects we want to show what the Apache Training project can
> > offer to those projects**.*
> >
> > *We should build on the assumption that synergy and network effects can
> > help us to increase the community around training and skill management
> > topics.*
> >
> >
> > *Three most important unfinished issues to address before graduating:*
> > 
> >
> >1. Improve the community participation (other Apache projects should
> >actively be linked to this project, since they "have the content")
> >2. *(Re)define the short-, mid-, and long-term goals of the project.*
> >3. *Select an approach to handle non coding / non document related tasks
> >(e.g., community related activities on events)*
> >4. *Create a strategy how this projects contributes to or is supported
> >by other Apache projects*
> >5. Create a tutorial on how the tools provided by this project can be
> >used to create own content
> >6. Review current policies around contribution review and releases to
> >find a pragmatic compromise
> >
> > *Are there any issues that the IPMC or ASF Board need to be aware of?*
> > 
> >
> > The Training Project needs more contribution from other Apache projects,
> > hence a clear communication strategy for interlinking existing projects
> > with the Apache Training project is needed.
> >
> > We need feedback from other Apache projects on the presentations and
> > trainings developed till now.
> >
> >
> >
> > *In order to improve this collaboration we suggest to investigate the
> > status of other project’s documentation in a systematic approach,
> > especially with an eye on available training related material.*
> >
> > *How has the community developed since the last report?*
> > 

Re: Access to Incubator Wiki - Submission of Podling report - Apache Training

[Lars Francke]

Hi Mirko,

I'm afraid I can't remember the procedure to get access to that Wiki
but I will read it now and move it there!

Thank you very much.

Cheers,
Lars

On Wed, Jul 5, 2023 at 2:25 PM Mirko Kämpf  wrote:
>
> Hello,
>
> I intend to submit the draft of the podling report to this page:
> *https://cwiki.apache.org/confluence/display/incubator/July2023#training
> *
>
> But unfortunately, I still have no write permission to this wiki.
> My username is: mirko.kae...@gmail.com
>
>
> Here is the draft in the *Apache Training Wiki:*
> https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#PodlingReports-July2023
> 
>
> And at the end of this mail is the full text of the draft.
>
> It has been shared on the project's developer list.
> No comments so far.
>
> Cheers,
> Mirko
>
>
>
>
>
> July 2023
>
> *Training
> *
>
> The Training project aims to develop resources which can be used for
> training purposes in various media formats, languages and for various
> Apache and non-Apache target projects.
>
> Training has been incubating since 2019-02-21.
>
> In June, we started adjusting the project goals. Besides a pure focus on
> content creation tools we have identified the need for two additional
> aspects:
> (1) For ASF processes some documentation exists, e.g.
> https://community.apache.org/contributor-ladder, but the ASF member journey
> is still a challenge for many new members, especially those with less
> coding experience.
> As a solution it has been suggested to provide training material for the
> following problems:
> * You've just graduated to a TLP. What are the challenges you will now face?
> * New committer onboarding
> * New PMC member onboarding
> * New PMC Chair onboarding
> * New board member onboarding
>
> (2) Creation of some general recommendations/guidelines for:
>  * managing/validation of training material contributions of arbitrary ASF
> projects
> has been propsed.
>
> Initial discussion of the topics have been started.
>
> *We expand our focus now on the following aspects:*
>
> *We have to work on strategies to increase the** participation and the
> visibility of the project and its goals.*
>
> *Besides requests** for contributions from individual contributors** from
> other Apache projects we want to show what the Apache Training project can
> offer to those projects**.*
>
> *We should build on the assumption that synergy and network effects can
> help us to increase the community around training and skill management
> topics.*
>
>
> *Three most important unfinished issues to address before graduating:*
> 
>
>1. Improve the community participation (other Apache projects should
>actively be linked to this project, since they "have the content")
>2. *(Re)define the short-, mid-, and long-term goals of the project.*
>3. *Select an approach to handle non coding / non document related tasks
>(e.g., community related activities on events)*
>4. *Create a strategy how this projects contributes to or is supported
>by other Apache projects*
>5. Create a tutorial on how the tools provided by this project can be
>used to create own content
>6. Review current policies around contribution review and releases to
>find a pragmatic compromise
>
> *Are there any issues that the IPMC or ASF Board need to be aware of?*
> 
>
> The Training Project needs more contribution from other Apache projects,
> hence a clear communication strategy for interlinking existing projects
> with the Apache Training project is needed.
>
> We need feedback from other Apache projects on the presentations and
> trainings developed till now.
>
>
>
> *In order to improve this collaboration we suggest to investigate the
> status of other project’s documentation in a systematic approach,
> especially with an eye on available training related material.*
>
> *How has the community developed since the last report?*
> 
>
>
>
> *Activity has started to grow since the last report. We again failed to
> provide the report on time, but this will change soon.Two persons joined
> our conversation on the dev-list (Eric and Rich).*
>
>
> *How has the project developed since the last report?*
> 
>
> An pro-active request for a content / 

Re: [VOTE] Release Apache Pekko(incubating) 1.0.0-RC3

[Ryan Skraba]

Just for the form here (more details in dev@pekko list)

+1 (binding)

This code is already very mature, I focused on the form and process to
getting this (very anticipated) release out!

Thanks so much for doing this work.  I look forward to seeing the other
pekko artifacts released!

Ryan



On Wed, Jul 5, 2023 at 1:12 AM PJ Fanning  wrote:

> Hello Incubator community,
>
> This is a call for a vote to release Apache Pekko(incubating) version
> 1.0.0-RC3.
>
> The Pekko community vote result:
>
> https://lists.apache.org/thread/dwfc5h4jdvwld4z6fhzm87x1fyrv3gw4
>
> The Pekko community vote thread:
>
> https://lists.apache.org/thread/gkn1b3mddgo82doj4c0f38o26wwbm0fs
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC3/
>
> This release has been signed with a PGP key available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
>
> Release Notes:
>
> https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Core+Release+Notes
>
> Git branch for the release:
>
> https://github.com/apache/incubator-pekko/tree/v1.0.0-RC3
> Git commit ID: 4ce1095b4b48f5cdd31342ab9f0950bd44a2829a
>
> Please download, verify, and test.
>
> We have also staged jars in the Apache Nexus Repository. These were
> built with the same code
> as appears in this Source Release Candidate. We would appreciate if
> users could test with these too.
> If anyone finds any serious problems with these jars, please also
> notify us on this thread.
>
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>
> In sbt, you can add this resolver.
>
> resolvers += "Apache Pekko Staging" at
> "https://repository.apache.org/content/groups/staging;
>
>
> The vote will be left open until 23:00 UTC on 8 July 2023.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about Apache Pekko, please see https://pekko.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
> To compile from the source, please refer to:
>
>
> https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
>
> Some notes about verifying downloads can be found at:
>
> https://pekko.apache.org/download.html#verifying-downloads
>
>
> Here is my +1 (binding).
>
> Ryan Skraba has also voted +1 (binding) on the Pekko community vote.
>
> Thanks,
>
> PJ Fanning (Apache Pekko PPMC member and Incubator PMC member)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (Incubating) 0.7.1 rc2

[Jia Fan]

+1,

I have checked:
- The checksums and signatures are validated
- The LICENSE and NOTICE are fine
- DISCLAIMER-WIP exists
- No binary files in the source release
- incubating in the name

Liu Xun  于2023年7月5日周三 15:35写道：

> +1 (binding) from me,
>
> I have checked the following items:
> - Incubating in name
> - LICENSE and NOTICE are fine
> - DISCLAIMER-WIP exists
> - All links are valid
> - No unexpected binary files
> - All ASF files have ASF headers
> - Can compile from source
>   `mvn clean install`
>
> On 2023/06/28 02:03:01 Jiafu Zhang wrote:
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Uniffle(Incubating)
> > version 0.7.1 rc2
> >
> > The Apache Uniffle community has voted on and approved a proposal to
> release
> > Apache Uniffle(Incubating) version 0.7.1 rc2
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Uniffle community vote thread:
> > • https://lists.apache.org/thread/rfp3cll7l5q6525xs5jths7d4f6t0kt0
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/hnt45glbdkl75gtgb9czbcbc0r9d19s7
> >
> > The release candidate:
> > • https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.7.1-rc2/
> >
> > Git tag for the release:
> > • https://github.com/apache/incubator-uniffle/tree/v0.7.1-rc2/
> >
> > Release notes:
> > • https://uniffle.apache.org/download/release-notes-0.7.1
> >
> > The artifacts signed with PGP key A5F1ABF0, corresponding to
> > jiafu...@apache.org, that can be found in keys file:
> > • https://downloads.apache.org/incubator/uniffle/KEYS
> >
> > As the DISCLAIMER-WIP shows, this release still left some license
> > problems, which will be gradually resolved during incubation.
> >
> > The vote will be open for at least 72 hours or until necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [] +1 approve
> > [] +0 no opinion
> > [] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache Uniffle (Incubating) community
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (Incubating) 0.7.1 rc2

[li gang]

+1 (binding)
I checked
- Files have the word incubating in their name.
- Checksums and signatures are valid.
- DISCLAIMER-WIP,LICENSE and NOTICE files exist.
- All source files have ASF license header if necessary.
- Needs to update the Notice year.

Please update the NOTICE year next release.

Jiafu Zhang  于2023年6月28日周三 10:03写道：

> Hello Incubator Community,
>
> This is a call for a vote to release Apache Uniffle(Incubating)
> version 0.7.1 rc2
>
> The Apache Uniffle community has voted on and approved a proposal to
> release
> Apache Uniffle(Incubating) version 0.7.1 rc2
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Uniffle community vote thread:
> • https://lists.apache.org/thread/rfp3cll7l5q6525xs5jths7d4f6t0kt0
>
> Vote result thread:
> • https://lists.apache.org/thread/hnt45glbdkl75gtgb9czbcbc0r9d19s7
>
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.7.1-rc2/
>
> Git tag for the release:
> • https://github.com/apache/incubator-uniffle/tree/v0.7.1-rc2/
>
> Release notes:
> • https://uniffle.apache.org/download/release-notes-0.7.1
>
> The artifacts signed with PGP key A5F1ABF0, corresponding to
> jiafu...@apache.org, that can be found in keys file:
> • https://downloads.apache.org/incubator/uniffle/KEYS
>
> As the DISCLAIMER-WIP shows, this release still left some license
> problems, which will be gradually resolved during incubation.
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [] +1 approve
> [] +0 no opinion
> [] -1 disapprove with the reason
>
> Thanks,
> On behalf of Apache Uniffle (Incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 


--
Best Regards

DolphinScheduler PMC
Gang Li 李岗

lgcar...@apache.org

Re: [VOTE] Release Apache Uniffle (Incubating) 0.7.1 rc2

[Zhankun Tang]

+1 (Binding). Thanks.

BR,
Zhankun

Liu Xun 于2023年7月5日 周三15:35写道：

> +1 (binding) from me,
>
> I have checked the following items:
> - Incubating in name
> - LICENSE and NOTICE are fine
> - DISCLAIMER-WIP exists
> - All links are valid
> - No unexpected binary files
> - All ASF files have ASF headers
> - Can compile from source
>   `mvn clean install`
>
> On 2023/06/28 02:03:01 Jiafu Zhang wrote:
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Uniffle(Incubating)
> > version 0.7.1 rc2
> >
> > The Apache Uniffle community has voted on and approved a proposal to
> release
> > Apache Uniffle(Incubating) version 0.7.1 rc2
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Uniffle community vote thread:
> > • https://lists.apache.org/thread/rfp3cll7l5q6525xs5jths7d4f6t0kt0
> >
> > Vote result thread:
> > • https://lists.apache.org/thread/hnt45glbdkl75gtgb9czbcbc0r9d19s7
> >
> > The release candidate:
> > • https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.7.1-rc2/
> >
> > Git tag for the release:
> > • https://github.com/apache/incubator-uniffle/tree/v0.7.1-rc2/
> >
> > Release notes:
> > • https://uniffle.apache.org/download/release-notes-0.7.1
> >
> > The artifacts signed with PGP key A5F1ABF0, corresponding to
> > jiafu...@apache.org, that can be found in keys file:
> > • https://downloads.apache.org/incubator/uniffle/KEYS
> >
> > As the DISCLAIMER-WIP shows, this release still left some license
> > problems, which will be gradually resolved during incubation.
> >
> > The vote will be open for at least 72 hours or until necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [] +1 approve
> > [] +0 no opinion
> > [] -1 disapprove with the reason
> >
> > Thanks,
> > On behalf of Apache Uniffle (Incubating) community
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (Incubating) 0.7.1 rc2

[Liu Xun]

+1 (binding) from me,

I have checked the following items:
- Incubating in name
- LICENSE and NOTICE are fine
- DISCLAIMER-WIP exists
- All links are valid
- No unexpected binary files
- All ASF files have ASF headers
- Can compile from source
  `mvn clean install`

On 2023/06/28 02:03:01 Jiafu Zhang wrote:
> Hello Incubator Community,
> 
> This is a call for a vote to release Apache Uniffle(Incubating)
> version 0.7.1 rc2
> 
> The Apache Uniffle community has voted on and approved a proposal to release
> Apache Uniffle(Incubating) version 0.7.1 rc2
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Uniffle community vote thread:
> • https://lists.apache.org/thread/rfp3cll7l5q6525xs5jths7d4f6t0kt0
> 
> Vote result thread:
> • https://lists.apache.org/thread/hnt45glbdkl75gtgb9czbcbc0r9d19s7
> 
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.7.1-rc2/
> 
> Git tag for the release:
> • https://github.com/apache/incubator-uniffle/tree/v0.7.1-rc2/
> 
> Release notes:
> • https://uniffle.apache.org/download/release-notes-0.7.1
> 
> The artifacts signed with PGP key A5F1ABF0, corresponding to
> jiafu...@apache.org, that can be found in keys file:
> • https://downloads.apache.org/incubator/uniffle/KEYS
> 
> As the DISCLAIMER-WIP shows, this release still left some license
> problems, which will be gradually resolved during incubation.
> 
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
> 
> Please vote accordingly:
> 
> [] +1 approve
> [] +0 no opinion
> [] -1 disapprove with the reason
> 
> Thanks,
> On behalf of Apache Uniffle (Incubating) community
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org