Re: [WG: Website] Proposal - Website working group

2024-02-10 Thread Christiano Anderson

I'd like to be part and contribute with this new WG

On 07/02/2024 17:11, Rich Bowen wrote:

Proposed: Form a formal Website working group.

(I am aware that I haven’t defined “working group” yet, and I do, in fact, 
intend to propose a Working Groups Working Group which could possibly formalize 
what a working group looks like. I have some ideas, but no desire to go define 
it on my own.)

The Website WG would, obviously, be responsible for the maintenance of the 
website. I am aware that some folks think I’m just off doing that on my own, 
and that’s part of what I’m trying to avoid (see 
https://lists.apache.org/thread/nwvr28gq51c8v0wkqjv8xvvc2xqrtf03 for further 
commentary). I would like to gather a group of people who 1) care about it and 
2) are willing to do some of (NOT ALL) the work.

Specific things that I believe we should tackle include

* Long-term maintenance of the site. This involves regular audits, implementing 
metrics, and perhaps other things
* Reorg - this is a short-term task that I’ve been just doing on my own, which 
ensures it will never get done, and if it did, there may be some disagreement 
about how I did it.
* Deduplication - work closely with MarkPub to figure out the *right* place for 
certain information; work through the policy/best-practice dichotomy and ensure that 
we are *not* duplicating policy docs; Work on content on www.a.o 
 that is closely related to content on community.a.o - which 
one is authoritative? Ensure that we don’t duplicate, contradict, or confuse.

There’s probably more.

I would hope that a WG would have regular checkins (could be email, Slack, 
Google Meet, I really don’t care, as long as everyone is engaging with the 
conversation.)

If you are interested in helping form this group, please speak up in this 
thread, and help us help one another.

—
Rich Bowen
rbo...@rcbowen.com







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



Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

2024-02-10 Thread tison
It seems that the repo is foundation-wise that I have the permission to
move forward this effort.

I'll push the branch and update the README. And then ask for INFRA to make
it the default branch, as well as setting the repo as a repo template.

I believe comdev and the Incubator are related to these actions so I post
here for visibility, and welcome any feedback if you second this or have
suggestions.

Best,
tison.


tison 于2024年2月4日 周日23:16写道:

> Hi,
>
> I finally find some time to prepare a demo for the new website template
> [1].
>
> It may still open to be improved including a download page template
> and a community page template, as well as some guides as its docs. But
> I'd like to first collecting feedback and finding which PMC is
> responsible for this repository [2].
>
> The background is that our current template is quite old and not
> updated for the past six years. Few people understand those techniques
> and have a hard time to build their own site. Also, new policy
> compliance and new techniques benefits can be included in the template
> to help new projects (podlings) build a wonderful site.
>
> I'm glad to maintain this repo but I find myself has no permission
> over this repo. So again, which PMC is responsible for this
> repository?
>
> Best,
> tison.
>
> [1] https://github.com/tisonkun/apache-website-template/tree/docusaurus
> [2] https://github.com/apache/apache-website-template/
>
> Alex Porcelli  于2024年1月30日周二 04:53写道:
> >
> > Another shout-out for tison and the Apache Fury to provide such a nice
> > starting point for new websites.
> >
> > I managed to put, for now, a simple placeholder website for Apache KIE
> > (incubation).
> >
> > Thank you tison and the Apache Fury community!
> >
> > On Fri, Jan 26, 2024 at 4:10 AM Xuanwo  wrote:
> > >
> > > > I managed to move our old website to Docusaurus in one day - using
> the template
> > > > structure from Fury, if you don’t mind.
> > >
> > > Congrats!
> > >
> > > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote:
> > > > Hey tison,
> > > >
> > > > Thank you for the head-up. I managed to move our old website to
> > > > Docusaurus in one day - using the template structure from Fury, if
> you
> > > > don’t mind. Awesome stuff, would love when we’d had a template for
> the
> > > > podlings to setup a good looking, SEO friendly project page. That’s
> > > > needed to grow the community!
> > > >
> > > > Cheers, thanks again,
> > > >  —Alex
> > > >
> > > >> On Jan 25, 2024, at 12:01, tison  wrote:
> > > >>
> > > >> Hi Alexander,
> > > >>
> > > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be
> > > >> straightforward to follow already. The most simple one now is
> > > >> https://github.com/apache/incubator-fury-site.
> > > >>
> > > >> Also, Docu is well-documented https://docusaurus.io/docs.
> > > >>
> > > >> I'm thinking of updating the website template [1] with Docu but have
> > > >> not yet had time and understand which PMC manages this project.
> > > >>
> > > >> Best,
> > > >> tison.
> > > >>
> > > >> [1] https://github.com/apache/apache-website-template
> > > >>
> > > >> Alexander Alten-Lorenz  于2024年1月25日周四
> 18:20写道:
> > > >>>
> > > >>> Hi Xuanwo,
> > > >>>
> > > >>> Thank you, highly appreciated! Do you have any how-to for setting
> Docusaurus up?
> > > >>>
> > > >>> —Alex
> > > >>>
> > >  On Jan 25, 2024, at 11:01, Xuanwo  wrote:
> > > 
> > >  Hi, alexander
> > > 
> > > > We aren't web designers and we would love to find helping hands
> to get
> > > > the page in order, including re-organizing and rewriting.
> > > 
> > >  I'm with the OpenDAL Community, and we also lack web designers.
> Our community
> > >  opted for Docusaurus[1], which we found easy to start with and
> set up. It
> > >  offers a decent theme suitable for open-source projects. For
> reference, you
> > >  can check out OpenDAL's homepage[2]. We hope our experience
> proves useful.
> > > 
> > >  [1] https://docusaurus.io/
> > >  [2] https://opendal.apache.org/
> > > 
> > >  On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote:
> > > > Hi incubator community,
> > > >
> > > > Would anyone be willing to help the Wayang project with our
> website?
> > > > We aren't web designers and we would love to find helping hands
> to get
> > > > the page in order, including re-organizing and rewriting.
> > > >
> > > > thank you, cheers,
> > > > --alexander
> > > 
> > >  --
> > >  Xuanwo
> > > --
> > > Xuanwo
>


Re: [WG: Sharpeners] Proposed - Sharpeners

2024-02-10 Thread Rich Bowen
Yes that's probably a good improvement. My one concern is that one
shouldn't have to be a technical expert in the project to do this work, so
careful wording is necessary.

Rich

On Fri, Feb 9, 2024, 20:49 Phil Steitz  wrote:

> Thanks, Rich.  I think we have been headed in this direction for some time
> now and something like this is needed.  Many thanks for coming up with a
> concrete proposal.
>
> I have one suggestion for improvement, which is in part a problem
> statement.  Instead of just subscribing to the private@ list, I would
> suggest that Sharpeners also subscribe to and even engage primarily on the
> dev@ list.  The problem statement part of this is that having influence
> "behind the curtain" of privacy runs counter to transparency, especially if
> that influence is on how the project is run.  It's been a while since I
> have been on the board, but I remember often pointing to discussions on
> private lists that should be public. I don't think its a good idea to have
> general discussion about how things are done in a project on private lists
> and having the Sharpeners engage exclusively there might encourage more of
> that.  I think its a best practice to post draft board reports to dev lists
> and relay board feedback there.  I know a lot of projects do that.  That
> way, the community understands the thought process and can lead whatever
> change is needed, rather than being surprised by it.   When I look back on
> successful "sharpenings" in the past, the real work generally happened on
> the project lists, with only very sensitive or individual people-related
> things being worked out on private lists.
>
> It might be a good idea to look at some historical examples and tease out a
> little more what exactly "sharpening" is going to be.  If it is primarily
> (re-)education or community transformation, that really does need to be
> public and community-based.  If its more admin / legal / policy compliance,
> that fits with the private engagement of the PMC model.
>
> Phil
>
>
>
>
>
>
> On Fri, Feb 9, 2024 at 6:55 AM Rich Bowen  wrote:
>
> > Ok, this one probably requires a LOT of discussion, but it’s something
> > I’ve been thinking about for more than a year, so if some of this seems
> > like I’ve already wordsmithed it, that’s why.
> >
> > Projects go through the Incubator, learn how to Apache, and then they
> move
> > on. The membership changes. The mission changes. The world changes around
> > them. And the lessons of the Incubator are often forgotten, or deemed
> > unimportant to the changed circumstances.
> >
> > This Working Group provides a mechanism for ASF Members to assist the
> > board in advising projects. (See the FAQ, “Why a member?” before
> objecting
> > to this. I am very firm on this point, and I believe that the board will
> be
> > too, if asked.
> >
> > I want to STRENUOUSLY encourage you to read the entire proposal before
> > responding, because I have foreseen a number of objections to this, most
> of
> > which go under the heading of “who are YOU to tell US what to do?!” I am
> > very cognizant of this. ComDev is a PEER to other projects, not in a
> > position of authority. That said, every member is responsible, to a
> certain
> > degree, for the direction the entire Foundation takes.
> >
> > I believe that this effort, if successful, could be hugely influential in
> > the trajectory of the ASF in the coming years. I believe that this is, at
> > heart, the primary mission of ComDev. I feel very strongly about the
> > importance of this working group. I will be glad to hold forth at greater
> > length over beer and/or scotch, at the next event facilitated by
> wg-social.
> > ;-)
> >
> > Anyways, please read
> >
> https://svn.apache.org/repos/asf/comdev/community/wg-sharpeners/README.md
> > and then think a little bit and then let me know what you think.
> >
> > Proposal also included below for convenience.
> >
> >
> >
> > # Sharpeners Work Group (Proposed)
> >
> > To provide "Sharpeners" - volunteers who come alongside a PMC to offer
> > an outsider's perspective on the project, and advice to build their
> > community.
> >
> > ## Who
> >
> > A Sharpener must be an ASF member. They are preferably a member who has
> > been around a while, and has some reason to be trusted as a mentor. You
> > must not already be a member of the PMC. You must not have any
> > adversarial reason to take on the role - a bone to pick, a corporate
> > entanglement, or whatever.
> >
> > ## What
> >
> > A Sharpener will subscribe to the project's PMC list
> > (priv...@project.apache.org) and mostly listen. They will comment
> > constructively when they see something that may be improved. They will
> > report concerns back to the board, via  sections in the ComDev
> > report, under a new "Workgroups" section that will be created for this
> > purpose.
> >
> > ## Values
> >
> > Interactions by Sharpeners are at the pleasure of the PMC. You do not
> > have any authority over the PMC.
> >
> > ##

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

2024-02-10 Thread tison
I've pushed the code to 'docusarus' branch on this repo, and file a
ticket on INFRA [1] to ask for some privileges actions.

Best,
tison.

[1] https://issues.apache.org/jira/browse/INFRA-25486

tison  于2024年2月10日周六 18:32写道:
>
> It seems that the repo is foundation-wise that I have the permission to move 
> forward this effort.
>
> I'll push the branch and update the README. And then ask for INFRA to make it 
> the default branch, as well as setting the repo as a repo template.
>
> I believe comdev and the Incubator are related to these actions so I post 
> here for visibility, and welcome any feedback if you second this or have 
> suggestions.
>
> Best,
> tison.
>
>
> tison 于2024年2月4日 周日23:16写道:
>>
>> Hi,
>>
>> I finally find some time to prepare a demo for the new website template [1].
>>
>> It may still open to be improved including a download page template
>> and a community page template, as well as some guides as its docs. But
>> I'd like to first collecting feedback and finding which PMC is
>> responsible for this repository [2].
>>
>> The background is that our current template is quite old and not
>> updated for the past six years. Few people understand those techniques
>> and have a hard time to build their own site. Also, new policy
>> compliance and new techniques benefits can be included in the template
>> to help new projects (podlings) build a wonderful site.
>>
>> I'm glad to maintain this repo but I find myself has no permission
>> over this repo. So again, which PMC is responsible for this
>> repository?
>>
>> Best,
>> tison.
>>
>> [1] https://github.com/tisonkun/apache-website-template/tree/docusaurus
>> [2] https://github.com/apache/apache-website-template/
>>
>> Alex Porcelli  于2024年1月30日周二 04:53写道:
>> >
>> > Another shout-out for tison and the Apache Fury to provide such a nice
>> > starting point for new websites.
>> >
>> > I managed to put, for now, a simple placeholder website for Apache KIE
>> > (incubation).
>> >
>> > Thank you tison and the Apache Fury community!
>> >
>> > On Fri, Jan 26, 2024 at 4:10 AM Xuanwo  wrote:
>> > >
>> > > > I managed to move our old website to Docusaurus in one day - using the 
>> > > > template
>> > > > structure from Fury, if you don’t mind.
>> > >
>> > > Congrats!
>> > >
>> > > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote:
>> > > > Hey tison,
>> > > >
>> > > > Thank you for the head-up. I managed to move our old website to
>> > > > Docusaurus in one day - using the template structure from Fury, if you
>> > > > don’t mind. Awesome stuff, would love when we’d had a template for the
>> > > > podlings to setup a good looking, SEO friendly project page. That’s
>> > > > needed to grow the community!
>> > > >
>> > > > Cheers, thanks again,
>> > > >  —Alex
>> > > >
>> > > >> On Jan 25, 2024, at 12:01, tison  wrote:
>> > > >>
>> > > >> Hi Alexander,
>> > > >>
>> > > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be
>> > > >> straightforward to follow already. The most simple one now is
>> > > >> https://github.com/apache/incubator-fury-site.
>> > > >>
>> > > >> Also, Docu is well-documented https://docusaurus.io/docs.
>> > > >>
>> > > >> I'm thinking of updating the website template [1] with Docu but have
>> > > >> not yet had time and understand which PMC manages this project.
>> > > >>
>> > > >> Best,
>> > > >> tison.
>> > > >>
>> > > >> [1] https://github.com/apache/apache-website-template
>> > > >>
>> > > >> Alexander Alten-Lorenz  于2024年1月25日周四 
>> > > >> 18:20写道:
>> > > >>>
>> > > >>> Hi Xuanwo,
>> > > >>>
>> > > >>> Thank you, highly appreciated! Do you have any how-to for setting 
>> > > >>> Docusaurus up?
>> > > >>>
>> > > >>> —Alex
>> > > >>>
>> > >  On Jan 25, 2024, at 11:01, Xuanwo  wrote:
>> > > 
>> > >  Hi, alexander
>> > > 
>> > > > We aren't web designers and we would love to find helping hands to 
>> > > > get
>> > > > the page in order, including re-organizing and rewriting.
>> > > 
>> > >  I'm with the OpenDAL Community, and we also lack web designers. Our 
>> > >  community
>> > >  opted for Docusaurus[1], which we found easy to start with and set 
>> > >  up. It
>> > >  offers a decent theme suitable for open-source projects. For 
>> > >  reference, you
>> > >  can check out OpenDAL's homepage[2]. We hope our experience proves 
>> > >  useful.
>> > > 
>> > >  [1] https://docusaurus.io/
>> > >  [2] https://opendal.apache.org/
>> > > 
>> > >  On Thu, Jan 25, 2024, at 16:26, Alexander Alten wrote:
>> > > > Hi incubator community,
>> > > >
>> > > > Would anyone be willing to help the Wayang project with our 
>> > > > website?
>> > > > We aren't web designers and we would love to find helping hands to 
>> > > > get
>> > > > the page in order, including re-organizing and rewriting.
>> > > >
>> > > > thank you, cheers,
>> > > > --alexander
>> > > 
>> > >  --
>> > >  Xuanwo