Re: [DISCUSSION] -- Hackernews style social media / blog site for planet apache
Hi, On Thu, Sep 26, 2024 at 12:07 AM Drew Foulks wrote: > ...I'd like to pitch the idea of reviving a planet apache of sorts as a reddit > / hackernews / lobste.rs style message board. ... Do you see this as a potential replacement for this list for example, or something else? I think Planet Apache was just a blog aggregator, back in the days, but it looks like you're speaking about a service where conversations can happen. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Some notes on ASF conferences.
Hi, On Mon, Jun 10, 2024 at 1:21 PM Claude Warren wrote: > ...Renaming the conference to "The ASFConference" or "ASFCon" would > go a long way to mitigating this problem... I agree that the current name is not good, but would also like to get rid of the "con" suffix which means "idiot", or worse, in French. I suggest "ASF Tech" or "ASF Tech & Community", but Naming Is Hard anyway. > ...The positioning is an issue... It's always been like that, because our communities are all over the place in terms of technology and tech culture. Which is not a problem otherwise. One thing that I hear repeatedly is that many of us get the most value from the "hallways conference", meeting our peers in person, spontaneously cross-pollinating ideas [1], etc. How to "sell" that so people get a travel budget to attend, I don't know. But for me that's the real value of the conference, and I think the ASF as a whole gets a lot of value out of that. The "ASF Hallways Conference" would be a surprising name indeed ;-) -Bertrand [1] For those who were part of the Maven chat in the Széchenyi baths a few years ago, that's a fantastic example! - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [WG: Code of conduct] Proposal
Hi, On Mon, Jun 10, 2024 at 3:33 PM Rich Bowen wrote: > ...Many ASF projects do not have a code of conduct, and push this up to the > Foundation. This mostly seems > to work, in practice, most of the time, but the public *perception* is just > that they don’t have one... I think this should be handled like https://security.apache.org/projects/ : projects CAN have their own code of conduct page and contact address, and if they don't they MUST point to the ASF's page and contact address -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [C/C Europe 25] [DISCUSS] Where to hold the conference
On Fri, May 3, 2024 at 7:37 AM Claude Warren wrote: > ...if you have opinions and/or ideas please speak up... I've been to several small/medium conferences in Berlin [1] in the last few years and it was always a great experience. Easy to travel to, including by train, reasonable costs most of the time (except when the marathon or similar events happen maybe), and we have a number of ASF members there who might help with contacts or more. -Bertrand [1] https://24.foss-backstage.de/ , https://adapt.to/2024/ , https://berlinbuzzwords.de - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Events calendar: help wanted
On Fri, Apr 19, 2024 at 2:13 PM Rich Bowen wrote: > ...I would *really* like to not have to edit ics files directly. That way > lies madness... Indeed. If someone wants to take a look, Hugo (which is used for both the comdev and events websites) does support the generation of iCal files directly from markdown files representing events. https://github.com/raoulb/hugo-ical-templates-demo looks like a good example of that, except that it's using a complicated date format in the Markdown event files. But that can certainly be fixed. -Bertrand (really in "someone should" mode here, won't probably have time to help right now) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: FYI, ASF volunteers page is live, mentors & speakers are welcome to sign up
On Wed, Mar 20, 2024 at 9:31 AM Roman Shaposhnik wrote: > ...does it get rebuilt automatically... Yes [1], although there might be some latency in kicking the build process, a few minutes IIRC. -Bertrand [1] https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
FYI, ASF volunteers page is live, mentors & speakers are welcome to sign up
Hi, The new "ASF volunteer mentors & speakers" page [0] is live, meant to replace the unmaintained community.zones.apache.org utilities, which will soon be redirected to it. ASF committers are welcome to add their names to that page if you are willing to be a mentor and/or speaker on ASF topics. To do so, add your ASF ID to [1] and if desired you can add some additional information (region, languages spoken, website) to [2]. -Bertrand [0] https://community.apache.org/contributors/asf-volunteers.html [1] https://github.com/apache/comdev-site/blob/main/source/contributors/asf-volunteers.md [2] https://github.com/apache/comdev-site/blob/main/static/data/people.json - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Web site checker needs help
On Wed, Feb 28, 2024 at 1:28 AM Craig Russell wrote: > ...Is it worth creating a new community-working-group-site-check to document > the issues with the tool?... Whimsy is created and managed by the https://whimsical.apache.org/ PMC, why not make that happen there? -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
How to redirect community.zones.apache.org to the new volunteers page?
Hi, Once [1] is merged we'll need to redirect the following URLs to it: - https://community.zones.apache.org/map.html - https://community.zones.apache.org (and more maybe, did I miss something?) I haven't touched that zone server in ages, maybe never, can someone help make that happen? The redirects should go to https://community.apache.org/contributors/asf-volunteers.html which is not live yet, but soon. IIUC the source code of those apps is at [2] but I haven't found information on how to access the zone that runs them. -Bertrand [1] https://github.com/apache/comdev-site/pull/146 [2] https://svn.apache.org/repos/asf/comdev/nearby_people/ - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
On Tue, Feb 20, 2024 at 1:20 PM tison wrote: > > > And/or just point to the source code of existing ASF websites which > > can serve as living examples. > > You can check the original mailing list thread [1]. I recommend Fury as an > example there because it's just started... The beauty of the ASF websites setup is that people can use any tool to build their website, as long as the output is static files, and there are many examples from our projects for the various tools. The existing https://infra.apache.org/project-site.html page lists a number of options, pointing to it could be useful, or we might suggest simplifying that page to expose only what ASF infra manages, and move the "website building options" to the comdev website. I am not against having a website template, but I don't think it's terribly useful and I don't want us to make people believe that there is a preferred option for building websites. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno wrote: > ...Just use the existing website-template repository, have the > default branch be an empty branch with a README that tells you what the > different examples are, each in their own branch or directory... And/or just point to the source code of existing ASF websites which can serve as living examples. And encourage people to add GitHub topics to their website repositories, so that queries like https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories can give you a list of real live examples that use your favorite website generation tool, "hugo" in this example. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [WG: Website] Proposal - Website working group
On Wed, Feb 7, 2024 at 5:11 PM Rich Bowen wrote: > ...I would hope that a WG would have regular checkins... I cannot commit to any synchronous work, but... > If you are interested in helping form this group, please speak up in this > thread, > and help us help one another... I'm happy to help and be part of this working group. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Board Report: Due date for Solr is Dec 13th or 20th?
Hi, On Mon, Dec 11, 2023 at 7:26 AM Ayush Saxena wrote: > > I went to the Reporter Wizard: https://reporter.apache.org/wizard/ and > see "Wed Dec 13 2023 (Report is due in 3 days)" > ...That must have taken into consideration that the board report needs to > be filled early enough that the directors can go through them before > the meeting... Yes, that's the idea. We usually do our best to also review reports that come later than that deadline, but the risk is a report being rejected as there wasn't enough time to review. > > ...should the reporting period cover 3 months as usual or 4 because of > the delay?.. Reports should cover everything that happened since the last report. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Nearby ASF people, or volunteers page?
On Mon, Nov 27, 2023 at 12:02 PM Bertrand Delacretaz wrote: > ...Unless people step up to actually maintain [1], I think [2] would at > least allow us to publish some up to date information. We can always > revive [1] later if volunteers show up... I got some positive feedback in this thread and no objections I think, so would be ready to merge [2]. The map thing can be added later if someone volunteers for that. But ideally we should redirect [1] and [4] to that page, can anyone help with that? If yes I'll merge [2] and we can then redirect and announce the new page for volunteers to sign up. -Bertrand > > [1] https://community.zones.apache.org/map.html > [2] https://github.com/apache/comdev-site/pull/146 > [3] > https://community-volunteers.staged.apache.org/contributors/asf-volunteers.html [4] https://community.zones.apache.org/ - even more stale variant of [1] - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [website] how to add an “edit in GitHub” link?
On Tue, Nov 28, 2023 at 12:15 AM sebb wrote: > ...Providing a link to the source page does mean an extra click to edit > the file, but it means one can still provide a patch if one does not > wish to subscribe to GH... I agree with that, created https://github.com/apache/comdev-site/pull/147 adding these links to page sources. Many thanks Sebb and Roy for the pointers! -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Nearby ASF people, or volunteers page?
On Mon, Nov 27, 2023 at 12:34 PM Roman Shaposhnik wrote: > ...This would work for me, but I'd really love to have a map > visualisation view as well.. I've now changed the structure [1] to have additional data about people in static/data/people.json, with just two fields (ASF ID and roles) in the Markdown file. This allows for easily adding more fields about people in the JSON file, for information that's not available elsewhere. -Bertrand [1] https://github.com/apache/comdev-site/pull/146/files - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[website] how to add an “edit in GitHub” link?
Hi, I'd like to add an "edit in GitHub" link to the pages of https://community.apache.org/ , like we have in Sling [1]. But I don't know how to do it with Hugo - before I dig too deep, does someone have an example? For some pages like [2] which are generated instead of being backed by a Markdown file, we'd need to either link to the repository home, or add no link. -Bertrand [1] https://sling.apache.org/documentation/development.html (at the bottom, "this page can be edited...") [2] https://community.apache.org/tags.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Nearby ASF people, or volunteers page?
On Mon, Nov 27, 2023 at 12:34 PM Roman Shaposhnik wrote: > ...This would work for me, but I'd really love to have a map > visualisation view as well > (this should't be too hard, right? ;-)).. Nothing's hard when you have a computer, patches welcome I guess ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Nearby ASF people, or volunteers page?
Hi, We have a "nearby ASF people" app at [1], meant to help people find mentors or ASF speakers, that's not really maintained and contains a lot of stale data. I think we could just use a website page to provide that information, and I've created a prototype at [2], example output at [3]. It's just an additional "mentors and speakers" page for our website, with a simple way for people to add their information in a Markdown page. What do people think, can we replace the people app with such a simple page? Unless people step up to actually maintain [1], I think [2] would at least allow us to publish some up to date information. We can always revive [1] later if volunteers show up. -Bertrand [1] https://community.zones.apache.org/map.html [2] https://github.com/apache/comdev-site/pull/146 [3] https://community-volunteers.staged.apache.org/contributors/asf-volunteers.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Is Apache to bring back some dead project to give a new live ?
Hi Manuel, On Wed, Nov 22, 2023 at 1:05 PM Manuel Lison wrote: > ...I have to ask some questions > in different open-source communities to bring back some dead projects, but > they seem not to be interested in keeping them alive by their developers... The ASF does not have its own developers, only our projects have developers. So unless an existing ASF project is willing to adopt the code in question, the only way to bring it to the ASF is to create a new project, see [1]. > ...These projects are related to the programming languages that I am learning > (C++ and C#) and they seem to abandoned a couple of years ago: > > - MonoDevelop (An IDE for C#, .Net development and some C# libraries). > - Anjuta IDE (C++ and IDE for other programming languages) ... The ASF does not have a technical strategy, on purpose, as our mission is to provide space and resources for our projects to exist, as opposed to developing specific types of software. Incubating an ASF project is really about community and governance, not as much about what the software does or even about its quality - but see [2]. To enter the incubator, a project needs at least an embryo of a community, so a first step would be to either form a community around those projects, or motivate their existing community, if any, to join the Incubator. As the projects that you mention seem to be IDEs, maybe there's a way to morph them into NetBeans extensions, that would be https://netbeans.apache.org/ Hope this helps! -Bertrand [1] https://incubator.apache.org/cookbook/ [2] https://community.apache.org/apache-way/apache-project-maturity-model.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: License
Hi, On Thu, Oct 26, 2023 at 9:07 AM Kelly Oglesbee wrote: > > I have a lot of apache licenses on my mobile device, but they have no > copyright name copyright year... Note that an Apache License does not necessarily mean the corresponding project is an ASF project. Many other open source projects also use that license. > I'm new and thinking of becoming a contributor, but I need to understand what > all these licenses are > for before I continue to proceed... Your phone should indicate which projects are behind those licenses. As for the ASF, https://projects.apache.org/ has a list of our projects. If you find one that interests you, best is to get in touch using their dev@.apache.org mailing list. Hope this helps, -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Tika parser not parsing email content
Hi, On Tue, Oct 10, 2023 at 12:52 PM Kashif Khan wrote: > ...I have been working on the Tika parser to parse a few text files and it has > been working fine until I have come to an issue... this list is for general community-related discussions, for Tika you'll have to ask on their own list, see https://tika.apache.org/mail-lists.html -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Centralise DOAPs?
Hi, On Fri, Sep 8, 2023 at 12:26 AM sebb wrote: > ...I think it would be worth considering setting up a central store for > DOAPs... As we require our projects to have a website anyway, wouldn't it be better to get that information from the project's homepage instead of a separate file ? As you mention, I think it's only the fields that rarely change that are actually useful: the project's description, a few useful URLs, programming language, communications channel URLs, project category, code repository and download URLs, that's probably all we need ? That info can be embedded in HTML, for example using elements, Open Graph [1] maybe, with some ASF-specific extensions such as og:asf:category ? This would put the information in a natural place for projects to maintain it, and Open Graph metadata has other benefits. OTOH this means writing a conversion layer that, starting from a list of *.apache.org subdomain names, grabs that data and converts it to a format that's useful for projects.a.o. Another option would be to embed the current DOAP format using a
Re: AW: AW: Changing the defaults for GitHub generated email titles?
Christofer Dutz wrote : > > ... Infra has been giving me quite some pushback on these changes... I think backing your request by a comdev pmc vote can help, as it's then a group representing multiple projects that makes the request, instead of just you. Bertrand
Re: Simple question: Project blogs
Hi, On Tue, Jul 11, 2023 at 12:13 AM Brian Proffitt wrote: > > Simply put, if I want to direct people to Apache project's blogs, I would > send them to... where?.. Right now I don't think that we have an answer, we used to have https://twitter.com/planetapache and http://planet.apache.org/ but not anymore. Maybe https://apache.org/blogs would be a good place, with a manually curated list of project blogs? Or list them at https://projects.apache.org/ adding metadata to the projects LDAP info What would be really useful IMO is an aggregated RSS feed to which our project blogs can be added, which I suppose planet.a.o was doing. -Bertrand (who recently restarted using RSS feeds and super happy about that) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Changing the defaults for GitHub generated email titles?
Hi Chris, On Fri, Jun 30, 2023 at 11:14 AM Christofer Dutz wrote: > ...In general, I would agree, but the problem is that we currently have a very > large number of unreadable lists Fixing this is a valid goal, but breaking automation that projects might have setup is very bad. I guess what's needed is a clear explanation of what's happening and why, with a strong recommendation to switch but a way for projects to opt out of that switch if they need to fix some automation. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Changing the defaults for GitHub generated email titles?
Hi, On Fri, Jun 30, 2023 at 9:50 AM Christofer Dutz wrote: > ...I had many discussions with folks at infra about changing the defaults, > but generally > met opposition. The general argument was, that there would be bots that > automatically > consume these emails and these would be confused if we changed the defaults... That's a totally valid concern IMO, but there might be two ways to change the defaults: a) change for all lists which don't have specific settings b) change for newly created lists from now on If b) is possible I think that's much safer, and ideally projects can opt-in to switch existing lists. > ...Quite a number of projects have adopted these settings: > Like StreamPipes: > https://lists.apache.org/list?d...@streampipes.apache.org:lte=4M This looks nice to me, which is unsurprising, as people know I'm a big fan of Tags Everywhere ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Community-run MVP programs at the ASF
On Thu, Jun 22, 2023 at 6:15 PM Justin Mclean wrote: > ...A project should give a commit bit to anyone who is currently committed to > the project +1, and "being committed" does not necessarily mean "committing code", there are other ways to be committed to a project. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Community-run MVP programs at the ASF
On Thu, Jun 22, 2023 at 3:09 PM Gary Gregory wrote: > > ...If we adopt a badge system, I hope it can be automated (a la github), > because I don't want to spend time reading or voting on who gets what badge... Again, nobody is talking about *requiring* ASF projects to do anything, what we're discussing is potential guidelines for projects who would voluntarily like to do that, and are ready to do the corresponding work. Of course, if somebody helps automate that work, they might earn a "robots herder" badge ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Community-run MVP programs at the ASF
On Thu, Jun 22, 2023 at 12:44 PM Gary Gregory wrote: > ...Badges are fun, sure, but is that how we want to spend our energy?... I'm not saying projects should do badges, what I'm saying is that iff a project wants to celebrate specific contributors achievements, badges might be a good idea. And the project has to do the work then, of course. For projects which have team pages such as [1], publishing badges isn't hard. -Bertrand [1] https://sling.apache.org/project-information/project-team.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Community-run MVP programs at the ASF
On Thu, Jun 22, 2023 at 12:39 AM Phil Steitz wrote: > ...I strongly disagree with the idea of designating "MVPs" at any level in the > ASF... Same here, I object to having "most valuable" titles in ASF projects, as it can be understood to mean others are less valuable. It's probably a cultural thing, I know "most valuable something" is common in the US and probably not understood as I do, but we have multiple cultures here so we need to be careful. The ASF aims to be *very* egalitarian, sometimes too much maybe, but that has served us well on multiple occasions. To me, the goal should be to recognize someone's achievements without implying that they are generally better than others. Better at a single thing maybe, but nobody's perfect. I see MVP has been replaced by "Ambassador" in the Cassandra document, that's better, but it still takes a single angle on someone's value, for example requiring that someone "Maintains 1 year of active experience in public speaking, organising events or publishing content on the project's channels". Some people might not be willing or able to do these things, yet make tremendous contributions to a project in other ways. I'd personally find a "fun badges" system better suited to rewarding people's varied sets of skills and engagements, from a community point of view that's orthogonal with ASF roles, ideally in a tongue-in-cheek style that prevents the badges from being given too much value. "Traveling Salesman", "Broken Tests Mechanic", "Memory Leaks Plumber" are the types of badges that come to mind, and can be celebrated to highlight someone's achievement without making that too serious. I'm commenting on this from an ASF-wide perspective, our projects are of course free to do many of their own things as long as it doesn't conflict with ASF values - but as the question was about "providing guidance to ASF projects" I thought that's useful. And yes, IMO providing such guidance definitely belongs to comdev, reminds me of https://community.apache.org/committers/funding-disclaimer.html -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Proposal: Consolidate the various pages about voting/deciding
On Tue, May 30, 2023 at 9:45 PM wrote: > > We have four pages that discuss decision making, voting, consensus, and > so on... Aaaargh, and none of them even link to https://www.apache.org/foundation/voting (though some other pages of the website do) > ...I'd like to consolidate, but would like to hear opinions as to whether > this is one page or two (or some other answer) before I get started... IMO one page is best, make sure to refer to https://www.apache.org/foundation/voting and avoid duplicating info between them, and add redirects for deleted pages. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Reporter.a.o needs the new Project States, how?
On Thu, May 25, 2023 at 6:02 PM Bertrand Delacretaz wrote: > ...Here's a patch, below, with minor text tweaks... I have now committed this patch, https://reporter.apache.org/wizard/ looks good to me, thanks Daniel for your help! -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Reporter.a.o needs the new Project States, how?
On Thu, May 25, 2023 at 5:39 PM Daniel Gruno wrote: > ...I've updated the steps and added a generator for that section > that spits out two lines with placeholders in them... Looks great, thank you very much! Here's a patch, below, with minor text tweaks. -Bertrand Index: site/wizard/steps.json === --- site/wizard/steps.json(revision 1910059) +++ site/wizard/steps.json(working copy) @@ -15,7 +15,7 @@ "id": "state", "icon": "bell", "description": "Project Status", -"help": "This section is intended for describing the current status of the project, and any issues that may require board attention. Project status:Please use the terminology outlined in this reporting guide to describe the current state of the project. Your project status can be: New: a top-level project that's just getting startedOngoing: With high, moderate or low activity, which you may quantify if appropriateDormant: Not much happening on the code, but at least 3 PMC members ready to engage if neededAt risk: Not enough active PMC members, or a significant number of contributors left the project, etc.Considering moving to the Attic: a project that's about to move to the Attic, or discussing thatIssues for the boardIf there are any specific issues the board needs to be aware of, please write them here. Otherwise, write \"There are no issues requiring board attention.\"Issues could be: The project is blocked by Infra on an issue.The project does not have sufficient oversight from the PMC.There are concerning trademark issues.", +"help": "This section is intended for describing the current status of the project, and any issues that may require board attention. Project state:Please use the terminology outlined in this reporting guide to describe the current state of the project. Your project state can be: New: a top-level project that's just getting startedOngoing: With high, moderate or low activity, which you may quantify if appropriateDormant: Not much happening on the code, but at least 3 PMC members ready to engage if neededAt risk: Not enough active PMC members, or a significant number of contributors left the project, etc.Considering moving to the Attic: a project that's about to move to the Attic, or discussing thatIssues for the boardIf there are any specific issues the board needs to be aware of, please describe them here. Otherwise, write \"Issues for the board: none.\"Typical issues could be: The project is blocked by Infra on an issue.The project does not have sufficient oversight from the PMC.There are concerning trademark issues.", "placeholder": "If issues, write them here, otherwise state that there aren't any!", "generator": "generate_project_state" }, - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Reporter.a.o needs the new Project States, how?
On Thu, May 25, 2023 at 5:07 PM Daniel Gruno wrote: > ...How about changing the "issues" section to be called "project status" > and have it contain both the current state and any blockers that concern > the board?.. That would work, but I'd like to keep the "there are no issues for the Board" statement, which is very clear. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Reporter.a.o needs the new Project States, how?
Hi, The Board recently added a requirement for projects to report on their state using a set of standard keywords such as New, Ongoing, At Risk etc. [1] https://reporter.apache.org/wizard/ needs to be modified to include this information in the reports that it generates. I'm not sure how to make these changes, IIUC we just need to modify the steps.json file [2] to define this new section, but I don't know how to test such changes. ...besides just pushing to production, which might not be too risky, starting from a copy of another step ? -Bertrand [1] https://www.apache.org/foundation/board/reporting (search for "project state") [2] https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk/site/wizard/steps.json - as an icon, fa-bolt might work - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Proposal: Consolidate redundant beginner pages
Hi, On Mon, May 15, 2023 at 8:45 PM wrote: > ...Thoughts/advice/objections solicited... This all looks good to me provided redirects are defined for pages which go away - thanks for taking care of this! -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Community related menu at main ASF site
On Thu, May 11, 2023 at 9:35 AM sebb wrote: > ...I believe site owners have a duty to maintain URLs where possible... +1, redirects for the comdev site can be added at [1], and should be for all deleted or moved pages. This being said, now that we have tags on the comdev site it's probably safer for external links to point to those when possible, such as https://community.apache.org/tags/gsoc.html -Bertrand [1] https://github.com/apache/comdev-site/blob/main/static/.htaccess - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [website] FYI, tag-based navigation added to community.a.o
Hi, On Thu, Apr 27, 2023 at 9:53 PM Andrew Wetmore wrote: > ...It would be great if the tags option became available in a drop-down list, > maybe beside the search bar... That might be a big list, but if someone wants to do that why not! -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [website] FYI, tag-based navigation added to community.a.o
Hi, On Fri, Apr 28, 2023 at 12:04 AM sebb wrote: > ...As per subsequent emails, there needs to be a way of finding the > tags.html page from the website, rather than having to read the > mailing list ... I have modified the "Home" menu to point to the tags pages + https://community.apache.org/tags/navigation.html where we can tag pages with "navigation" to mark them as site navigation helpers. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[website] FYI, tag-based navigation added to community.a.o
Hi, I meant to activate this in a preview branch first, but that didn't work as Hugo generates absolute URLs for the tag navigation. So I have committed my tag-based navigation changes to our website, you can start at https://community.apache.org/tags.html to see how it looks. Feedback is welcome, and if this broke anything it's easy to revert! I have added an initial set of tags to some pages [1], feel free to add more, trying to reuse existing tags as much as possible. I'm a big fan of tag-based navigation, as menu-based usually only fits a single mental model, with tags it's much easier to discover related content. -Bertrand [1] https://github.com/apache/comdev-site/commit/3bb0a6382cda77f31d211e82eac5270f73d58906 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Best Practice documentation
Bertrand Delacretaz wrote: > ...hopefully we can fix that soon. The site staging feature should work now, this branch for example: https://github.com/apache/comdev-site/tree/preview/0421b is staged at: https://community-0421b.staged.apache.org/ Preview branches must have names that match the /preview\/[a-zA-Z0-9_]+$/ regexp. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Best Practice documentation
Bertrand Delacretaz wrote: > ...hopefully we can fix that soon... The jena-site Jenkinsfile [1] looks like it would publish staging branches, but uses a fixed target branch name, which I guess means that the last built branch wins. I suppose computing the staging branch name based on env.BRANCH_NAME would fix that. -Bertrand [1] https://github.com/apache/jena-site/blob/main/Jenkinsfile - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Best Practice documentation
Hi Rich, wrote: > On Thu, 2023-04-20 at 15:43 +0200, Bertrand Delacretaz wrote: > > Note that you can commit to a comdev-site branch named > > preview/... > Could you possibly explain to me specifically how to do this? My Git-fu > is failing me. I tried to prepare a preview branch for you but it looks like that feature is currently broken on comdev-site. Sorry about the noise, and hopefully we can fix that soon. In a pinch, if you render the content yourself and push it to a branch named rich-staging (with index.html at the root) it should appear at https://community-rich.staged.apache.org -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-529) Migrate blogs.apache.org/comdev to community.apache.org/blog
[ https://issues.apache.org/jira/browse/COMDEV-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714668#comment-17714668 ] Bertrand Delacretaz commented on COMDEV-529: I have prepared the blog section at https://community.apache.org/blog/ , "heavily inspired" from the security.a.o blog setup, commit [de3b576|https://github.com/apache/comdev-site/commit/de3b576e0e4f0984adc1b0ea388ce56f3ee863ca] > Migrate blogs.apache.org/comdev to community.apache.org/blog > > > Key: COMDEV-529 > URL: https://issues.apache.org/jira/browse/COMDEV-529 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > > As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the > [https://blogs.apache.org/comdev/] blog needs to move to another platform, > before May 31st. > I think the simplest is to move the content under > [https://community.apache.org/blog] by converting it and copying it under > [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" > folder. > For now I have saved a [raw HTML > copy|https://github.com/apache/comdev-site/blob/main/archives/comdev-blog-html-export-2023-04-20.zip] > of the existing content, but it looks like ASF infra can provide a more > convenient Markdown export, I have asked for that at INFRA-24484 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-529) Migrate blogs.apache.org/comdev to community.apache.org/blog
[ https://issues.apache.org/jira/browse/COMDEV-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated COMDEV-529: --- Description: As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the [https://blogs.apache.org/comdev/] blog needs to move to another platform, before May 31st. I think the simplest is to move the content under [https://community.apache.org/blog] by converting it and copying it under [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" folder. For now I have saved a [raw HTML copy|https://github.com/apache/comdev-site/blob/main/archives/comdev-blog-html-export-2023-04-20.zip] of the existing content, but it looks like ASF infra can provide a more convenient Markdown export, I have asked for that at INFRA-24484 was: As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the [https://blogs.apache.org/comdev/] blog needs to move to another platform. I think the simplest is to move the content under [https://community.apache.org/blog] by converting it and copying it under [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" folder. For now I have saved a [raw HTML copy|https://github.com/apache/comdev-site/blob/main/archives/comdev-blog-html-export-2023-04-20.zip] of the existing content, but it looks like ASF infra can provide a more convenient Markdown export, I have asked for that at INFRA-24484 > Migrate blogs.apache.org/comdev to community.apache.org/blog > > > Key: COMDEV-529 > URL: https://issues.apache.org/jira/browse/COMDEV-529 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > > As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the > [https://blogs.apache.org/comdev/] blog needs to move to another platform, > before May 31st. > I think the simplest is to move the content under > [https://community.apache.org/blog] by converting it and copying it under > [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" > folder. > For now I have saved a [raw HTML > copy|https://github.com/apache/comdev-site/blob/main/archives/comdev-blog-html-export-2023-04-20.zip] > of the existing content, but it looks like ASF infra can provide a more > convenient Markdown export, I have asked for that at INFRA-24484 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-529) Migrate blogs.apache.org/comdev to community.apache.org/blog
[ https://issues.apache.org/jira/browse/COMDEV-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714615#comment-17714615 ] Bertrand Delacretaz commented on COMDEV-529: I have assigned this to myself to it doesn't fall through the cracks, but if someone wants to work on it you are very welcome! As a example, https://security.apache.org/blog/ uses Hugo, source at https://github.com/apache/security-site/ > Migrate blogs.apache.org/comdev to community.apache.org/blog > > > Key: COMDEV-529 > URL: https://issues.apache.org/jira/browse/COMDEV-529 > Project: Community Development > Issue Type: Task > Components: Website > Reporter: Bertrand Delacretaz > Assignee: Bertrand Delacretaz >Priority: Minor > > As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the > [https://blogs.apache.org/comdev/] blog needs to move to another platform. > I think the simplest is to move the content under > [https://community.apache.org/blog] by converting it and copying it under > [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" > folder. > For now I have saved a [raw HTML > copy|https://github.com/apache/comdev-site/blob/main/archives/comdev-blog-html-export-2023-04-20.zip] > of the existing content, but it looks like ASF infra can provide a more > convenient Markdown export, I have asked for that at INFRA-24484 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-529) Migrate blogs.apache.org/comdev to community.apache.org/blog
[ https://issues.apache.org/jira/browse/COMDEV-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated COMDEV-529: --- Description: As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the [https://blogs.apache.org/comdev/] blog needs to move to another platform. I think the simplest is to move the content under [https://community.apache.org/blog] by converting it and copying it under [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" folder. For now I have saved a [raw HTML copy|https://github.com/apache/comdev-site/blob/main/archives/comdev-blog-html-export-2023-04-20.zip] of the existing content, but it looks like ASF infra can provide a more convenient Markdown export, I have asked for that at INFRA-24484 was: As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the [https://blogs.apache.org/comdev/] blog needs to move to another platform. I think the simplest is to move the content under [https://community.apache.org/blog] by converting it and copying it under [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" folder. For now I have saved a raw HTML copy of the existing content, but it looks like ASF infra can provide a more convenient Markdown export, I have asked for that at INFRA-24484 > Migrate blogs.apache.org/comdev to community.apache.org/blog > > > Key: COMDEV-529 > URL: https://issues.apache.org/jira/browse/COMDEV-529 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Bertrand Delacretaz >Assignee: Bertrand Delacretaz >Priority: Minor > > As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the > [https://blogs.apache.org/comdev/] blog needs to move to another platform. > I think the simplest is to move the content under > [https://community.apache.org/blog] by converting it and copying it under > [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" > folder. > For now I have saved a [raw HTML > copy|https://github.com/apache/comdev-site/blob/main/archives/comdev-blog-html-export-2023-04-20.zip] > of the existing content, but it looks like ASF infra can provide a more > convenient Markdown export, I have asked for that at INFRA-24484 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Assigned] (COMDEV-529) Migrate blogs.apache.org/comdev to community.apache.org/blog
[ https://issues.apache.org/jira/browse/COMDEV-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned COMDEV-529: -- Assignee: Bertrand Delacretaz > Migrate blogs.apache.org/comdev to community.apache.org/blog > > > Key: COMDEV-529 > URL: https://issues.apache.org/jira/browse/COMDEV-529 > Project: Community Development > Issue Type: Task > Components: Website > Reporter: Bertrand Delacretaz > Assignee: Bertrand Delacretaz >Priority: Minor > > As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the > [https://blogs.apache.org/comdev/] blog needs to move to another platform. > I think the simplest is to move the content under > [https://community.apache.org/blog] by converting it and copying it under > [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" > folder. > For now I have saved a raw HTML copy of the existing content, but it looks > like ASF infra can provide a more convenient Markdown export, I have asked > for that at INFRA-24484 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-529) Migrate blogs.apache.org/comdev to community.apache.org/blog
Bertrand Delacretaz created COMDEV-529: -- Summary: Migrate blogs.apache.org/comdev to community.apache.org/blog Key: COMDEV-529 URL: https://issues.apache.org/jira/browse/COMDEV-529 Project: Community Development Issue Type: Task Components: Website Reporter: Bertrand Delacretaz As per [https://lists.apache.org/thread/hfhzochhmqhd32tclgc47d5nk90jxmb2] the [https://blogs.apache.org/comdev/] blog needs to move to another platform. I think the simplest is to move the content under [https://community.apache.org/blog] by converting it and copying it under [https://github.com/apache/comdev-site/tree/main/source] in a new "blog" folder. For now I have saved a raw HTML copy of the existing content, but it looks like ASF infra can provide a more convenient Markdown export, I have asked for that at INFRA-24484 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Best Practice documentation
Hi Rich, wrote: > ...I appreciate your consideration. I know it's a big patch Note that you can commit to a comdev-site branch named preview/ to get a staged preview, which might be easier for people to review. The https://github.com/apache/comdev-site/tree/preview/test2-staging branch for example is staged at https://community-test2.staged.apache.org/ -Bertrand -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Donating a project to ASF
Hi, David Mariassy wrote: > ...If you have any > guidelines on how to go about potentially converting Shopify/sarama into > apache/sarama, please let me know!.. https://incubator.apache.org/cookbook/ explains how the ASF Incubator works and which projects are likely to fit. It's about the community really, so assuming the current owners are willing to donate the code to the ASF, what's needed is a community to make it happen. Looking at recent project statistics [1] the activity seems low in the last two years, with two people sharing the vast majority of commits. Not sure if that's sufficient to foster a viable ASF community, especially if the project's main sponsor is going away. >From a formal point of view, a viable ASF project needs at least three active PMC (Project Management Committee) members, so less than say 5 active committers rarely works. Donating the code to an existing ASF project might be a good option if one of our projects is willing to accept it. Having some of the existing contributors indicate that they are willing to continue maintaining that code obviously helps in that case. -Bertrand [1] https://github.com/Shopify/sarama/graphs/contributors?from=2021-02-20&to=2023-04-12&type=c - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Standardise on 'main' as the default branch?
sebb : >... Does anyone have any objections to my proposal to change the default > branch for comdev-site to main? .. I'm not opposed to that as long as you check that it doesn't break things. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Purpose of YAML files under speakers/talks
Hi Shane, Shane Curcuru wrote: > ...Everyone: Would this be useful - to have an easy to update list of > useful presentations - or not?... There's https://community.apache.org/speakers/slides.html which mostly duplicates that, without using the data file AFAICS. Even that page is not really up to date, with the last significant commit from 2020. So I don't think the speakers/talks/ data is useful, to me the problem is that none of us are actively shepherding that content, so having less stuff to maintain is better. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Thoughts From a Newcomer
Hi Melissa, Melissa Foulks wrote: > ...I've put together some thoughts about my experience thus far, and > some suggestions for how to potentially make onboarding easier for the new > volunteer... This is great, thank you! I'd say the ASF is a do-ocracy, things happen when people step up to make them happen. Which means that if you are willing and able to improve things, contributions are very welcome! The content of the apache.org is at https://github.com/apache/www-site ,and for community.a.o it's at https://github.com/apache/comdev-site You need some Markdown and Git knowledge to prepare change suggestions for that content, but it's not rocket science. HTH, -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [Proposal] ASF Fediverse/ActivityPub instance
Hi, Sam Ruby wrote: > > TL;DR: given a set of moderation guidelines and volunteers to > administer them, I'm willing to set up and host an ASF > Fediverse/ActivityPub instance on fly.io... Do you mean to open this to everybody who has an @apache.org account? Or just for a few official handles like announce@, TheASF@ ? If the latter, the moderation work might be much lower. Or maybe setting up *two* services makes sense, people.s.a.o and foundation.s.a.o, with the latter being more critical but less costly to operate from a moderation point of view. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Question about Apache projects and Kickstarter-like campaigns
Maria Elena Quiles López wrote: > On 2013/10/04 19:15:32 Thiago H de Paula Figueiredo wrote... Looks like an old message that resurfaces here - the example disclaimers at [1] cover such things. -Bertrand https://community.apache.org/committers/funding-disclaimer.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Tidelift
Ralph Goers wrote: > ...I personally have no problem having a project support page > that lists the individuals who accept GitHub sponsorships. Likewise I > think it would be OK to list the people who are accepting sponsorship from > Tidelift +1, and IMO such pages should include a disclaimer that there's no guarantee that the contributions of sponsored committers will be accepted by the project, like at [1] maybe. That's obvious for ASF community members, but maybe not for their sponsors. -Bertrand [1] https://community.apache.org/committers/funding-disclaimer.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: reporter.a.o seems broken
Hi, Xiangdong Huang wrote: > ...If it can not be fixed quickly, does anyone know how to submit the > project report?.. I _think_ PMC chairs can submit reports directly at https://whimsy.apache.org/board/agenda/ once the agenda for the meeting in question is prepared. Worst case you can send your report to board@a.o with a subject line like "[REPORT] Apache Foo - September 2022" -Bertrand -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] M&P discussions on comdev list?
Joe Brockmeier wrote: > tl;dr version: I'd like to start encouraging discussions related to > M&P on the ComDev list since there's a lot of potential overlap and > areas of collaboration I like the idea, keeping in mind that this must is public but I suppose that's good for the vast majority of topics. Bertrand
Re: [Question]About promotion ambassador
Le ven. 13 mai 2022 à 17:44, Geertjan Wielenga a écrit : > ...What I’m suggesting is that the denotation of “advocate” (on top of or > separate from alternative denotations) and a list of those friendly people > who might want to collaborate in the outside non-code world might be nice Projects are free to do things like that, and if they find it useful it's nice to share the ideas, for example in foundation or comdev blog posts. But I don't think we need an official ASF status for such things, it's just an informal (and important) community thing. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [Question]About promotion ambassador
Hi, Le ven. 13 mai 2022 à 17:06, Geertjan Wielenga a écrit : > > I like the idea because then I’d know who of the committers to reach out to > around advocacy specifically instead of code... One of my basic principles in ASF projects is to ask the project, not specific people. So in such a case I would write to the dev list with an [advocacy] subject line tag. Back to the original question, it's totally fine to have committers who do not write code but are "committed" to helping the project. Many projects have such committers. Projects are always free to make up their own informal roles, but from the ASF's point of view I think committer and PMC member are sufficient. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: It’s time to change the name
Hi, (Bcc people who have been active in the wiki page mentioned below) Le ven. 29 avr. 2022 à 16:14, Andrew Musselman a écrit : > ...Can I propose an outreach to some Apache tribe governments so we can open a > dialog with them directly, and start to understand what their official > experience of the ASF branding is?... I think that would be very useful, helping us hear from leaders who have standing in the cause. Note that this was discussed earlier at [1] which has an initial list of Apache Nations that could be contacted. Access restricted to ASF members as the page contains contact information. If a team of ASF members wants to make this happen, I'm willing to bring the topic to the Board and would support giving that team an official status to help them do that outreach. Next step would be for you and other interested Members to form a team and present their action plan to the Board. -Bertrand [1] https://cwiki.apache.org/confluence/display/ASFP/Outreach+to+the+Apache+Nations - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
-Hi, Le mar. 3 mai 2022 à 19:31, Craig Russell a écrit : > I could not find where we decided whether to use members@ or members-notify@ but I approved it. > If anyone objects to the mail list, we can have that discussion for next time I do object to using members-notify@ for those news, as that's outside of the scope defined at [1]. That list was created "for the limited purpose of sending formal notifications to the membership as a whole", because some members clearly expressed their objection to getting "too much email" from the ASF. Another objection has been raised on board@, let's discuss there. Going forward I suggest sending to members@ with a [NEWS] subject line header. And don't get me wrong, I like this initiative! -Bertrand [1] https://www.apache.org/foundation/records/minutes/2020/board_minutes_2020_05_20.txt - search for "members-notify"
Re: Idea: Monthly Members Moment/Critical Committer Communications
Hi, Le mar. 3 mai 2022 à 08:22, Christian Grobmeier a écrit : > Is the move to the new privacy policy interesting enough to be added to the > bullet points? > It’s a boring topic topic too many but maybe worth to mention due to its > impact on websites.. Definitely worth mentioning IMO. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Hi, Le mar. 5 avr. 2022 à 15:21, Rich Bowen a écrit : > ...AFAIK, while there are a few things in the current draft > that are not open to the public (ie, board meeting for example) there's > no harm in informing the public - they just cannot participate... I agree in principle, but we should clarify whether we are ok with publishing private URLs. Those are protected and there's already a good number of them out there, but I think it's good to define, as a general principle, whether we are ok with publishing URLs that only ASF members have access to. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Le lun. 4 avr. 2022 à 19:16, Priya Sharma a écrit : > > I am also not able to view those pages (perhaps only ASF members have > access)... That's correct, the ASFP wiki space is restricted to ASF members. It's not fantastic that we're discussing here and not letting people see that draft - OTOH that's more motivation to create a public version of those news, which would be a good thing. We might just send the public version here. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Hi, Sam Ruby wrote: >... Accordingly, I've taken the sample newsletter and posted it here: > https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022 > ... I've changed the structure slightly, with https://cwiki.apache.org/confluence/display/ASFP/Member+Moments being the homepage of those (work-in-progress, restricted to ASF Members) newsletters, displaying a list of its child pages. And moved your suggested content to https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022 accordingly. I hope it works for you - Cunningham's law implies that what you initially post is wrong so I had to fix it ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Java 17 Compatibility
Hi, Le mar. 29 mars 2022 à 08:46, Shivaraj Sivasankaran a écrit : > ...Please let us know the plan/roadmap of upgrading to java 17... Such things are not managed at the Apache Software Foundation level, all our projects manage that themselves. You can find a list of our projects at https://www.apache.org/index.html#projects-list , with links to their homepages that will allow you to contact them. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Idea: Monthly Members Moment/Critical Committer Communications
Hi, Le mar. 22 mars 2022 à 17:46, Rich Bowen a écrit : > ...1) Pitch this to the membership to determine whether this should land > on members@ or members-notify@.. I think it's clearly members@ - the other list is meant for "formal notifications" [1], with minimal traffic. With a suitable subject line header such as [news] maybe. -Bertrand [1] https://whimsy.apache.org/board/minutes/Create_members_notify.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Inquiry and Request for Guidance
Hi, For some reason the previous message in this thread was truncated between the moderation queue and here, here's the missing part: >I would like to make a few inquiries and seek your guidance: >- how may i propose a/some new projects for the developers to consider in >building? >- we would like to make contribution if the above request materializes, how do >we contribute to a specific project especially to the team involved? > Thank you, look forward to hear from you soon. and here's my reply: New projects come to the ASF via our Incubator - https://incubator.apache.org/cookbook/ is a good starting point to understand how that works. To contribute to a specific project (the ASF has about 300 of them) see that project's page, we have a list at https://www.apache.org/index.html#projects-list -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Effective ways of getting individuals funded to work on ASF projects
Hi, Le mer. 2 mars 2022 à 15:19, Roman Shaposhnik a écrit : > ...Once we've collected that type of info -- we can then sort of "evaluate > vendors" against that list and see what they are missing, etc. We can > even issue a wide "call to apply" for various companies if we feel like it... +1, I like the idea! -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Thoughts on alternative communication channels for our communities
Le mar. 1 mars 2022 à 23:05, Bill Cole a écrit : > ...I would actively oppose anything at the foundation level that requires > contributors to have *any* account with *any* specific 3rd party for > full participation... Good point, agreed, and that needs to be part of our requirements if we want to allow more channels for official communications of our projects. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Thoughts on alternative communication channels for our communities
Le mar. 1 mars 2022 à 20:12, Mark Thomas a écrit : > ...Why re-invert the wheel? > > https://matrix.org/ ... Would we need to run our own Matrix servers if we want to make it an alternative for our projects? Using https://matrix.org/docs/projects/server/synapse ? (which is written in Python - good thing for us as that's ASF infra's default language) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Effective ways of getting individuals funded to work on ASF projects
Hi, Le lun. 28 févr. 2022 à 21:15, Jarek Potiuk a écrit : > ...Proposal: > I think we all agree that ASF meets the criteria of Tidelift already. > Why don't Tidelift (in the places where open-source projects included are > listed) explain that ASF projects meet the criteria, and any one is free > to deal directly with the committers of all ASF projects directly... I'd say we all agree that *in theory* ASF projects meet Tidelift's criteria, quoting from earlier in this thread, with my own numbering added: Le lun. 28 févr. 2022 à 19:30, Joshua Simmons a écrit : > ...*What Tidelift expects from maintainers*Maintainers provide two things to > our customers: (1) information (licensing details, context on CVEs) and > (2) continuity (comfort that the package is maintained and is highly likely to > continue to be maintained). We also expect maintainers (3) to abide by a Code > of Conduct I think for (3) we're good, the ASF will intervene if projects are not ok. But for (1) and (2) I think the ASF *wants* our projects to be good citizens, and we work towards that and support them, but entities such as Tidelift or others could add value by measuring and reporting what actually happens. Does Apache FOO actually provide good information on security issues and CVEs? Timely response? What's their average/min/max response time, how many "in-flight" CVEs? Does Apache FOO release often enough? Maybe based on project maturity categories, new, established, mostly dormant etc. We could of course measure these things ourselves, and we do have some data. But I think having external entities provide factual data on how well our projects are doing can be useful, and for customers of Tidelift and the like that certainly has value. Whatever mechanism our contributors use to finance themselves, having information on which projects are most worthy of trust can help end users select and finance the right projects and people. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Effective ways of getting individuals funded to work on ASF projects
Hi, Le lun. 28 févr. 2022 à 11:06, Jarek Potiuk a écrit : >...the relationships I have is direct relationship with the > stakeholders. Let's deel, GitHub Sponsors, SAP Ariba are merely "removing > bureaucratic obstacles" but they are not "between" me and my stakeholders. > They are "on a side". They get a small cut sometimes (which I gladly pay) > but I want to talk to the stakeholders directly without any intermediaries > and establish a long-term relationship with them as an individual I think that's a key point, and listing such requirements for platforms that can help our contributors get funding sounds useful. Here's a quick list of initial requirements that we might include: -Contributors can get steady funding for their work -ASF is out of the loop of financial transactions -Contributors must use a standard ASF disclaimer (draft at [1]) -Contributors can establish a direct relationship with sponsors -Several "funding intermediaries" are available -ASF might define the wording that contributors can use when advertising themselves (based on facts, etc.) I like the idea of the ASF facilitating these things. Maintaining a comdev page that lists criteria like the above, with pointers to the relevant ASF policies, and lists intermediaries that our contributors have successfully used, might be a good start. -Bertrand [1] https://community.apache.org/committers/funding-disclaimer.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Thoughts on alternative communication channels for our communities
Hi Jarek, Le dim. 27 févr. 2022 à 23:11, Jarek Potiuk a écrit : > ...I use slack for async communication a lot. Including > underrepresented in IT Outreachy (https://www.outreachy.org/) interns that > I am mentoring - from India, Peru and Nigeria that I am interacting with > them over the last 3 months of their internship Most of that is > asynchronous because I live in Poland which is about 12 hours apart from > both India and Peru. And we have different holidays schedules... I think what you're describing is 1:1 async communications, or "1 to very small group". This is much easier to manage on any channel than "talking to the group" which is IMO required for Apache-style development. What I mean is: -Everybody sees the topics of all conversations fly by -It's easy to ignore specific or most conversations -It's easy to catch up after N days of absence while the rest of the team has been active, by quickly skimming the thread's subject lines -It's easy to use Precise Quoting in replies to enable deep conversations To me, the lack of first-class discussion threads, including a subject line, in most chat-style channels makes it hard to support that style. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Thoughts on alternative communication channels for our communities
Hi, Le mer. 16 févr. 2022 à 13:50, Roman Shaposhnik a écrit : > ...while the classical ASF communication culture is pretty squarely > centered around mailing lists it has become apparent in recent > years that some of our communities (especially younger ones) > prefer using alternative channels of communication I agree, and the risk with sticking with "if it didn't happen on the mailing list it didn't happen" is that some projects route around that, just play lip service to it but use other channels for their actual work. I think that is happening today, to various degrees. One way to avoid that would be to replace that dogma with more realistic criteria that can be met with other tools, similar to what Mark Thomas mentions in this thread, letting each project select the tools that work best for them within those boundaries. Things like: -Project channels must be public, async, archived on ASF-owned services and searchable -Project channels must be usable with open source clients (hmmm..Slack?) -All decisions and votes must be documented on the project's mailing list, with links to the original discussion. I think such a list of criteria (to be refined) would give our projects more leeway while respecting our actual goals in terms of open communications. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: SuccessAtApache blog offer
Hi Etienne, Le ven. 18 févr. 2022 à 10:43, Etienne Chauchot a écrit : > ...Any news about this proposal ? Can I start writing the blog post ? ... I don't have decision power on what's published in "Success at Apache" but I'd say go for it! An actual draft is IMO the best way to convince people, and if they're not convinced there's lots of other places where you can post. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Struts Jar and Use of Maven Versions Set Plugin.
Hi, On Mon, Nov 29, 2021 at 9:22 AM Warren Bates wrote: > ...We would like to know if there are any security concerns with the 1.3.8 > version of struts jar > in relation to this particular use case (Maven Versions Set plugin)?.. That's a question for the Struts project, http://struts.apache.org/mail.html This list is for general community management questions, as opposed to project-specific technical ones. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-431) invalid ticket
[ https://issues.apache.org/jira/browse/COMDEV-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz closed COMDEV-431. -- Resolution: Invalid > invalid ticket > -- > > Key: COMDEV-431 > URL: https://issues.apache.org/jira/browse/COMDEV-431 > Project: Community Development > Issue Type: New Feature >Reporter: denideniel >Priority: Major > Attachments: Titu39 OSTS OFFIC 365.jpg > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-431) How does Stella converts ost to PST software functions?
[ https://issues.apache.org/jira/browse/COMDEV-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated COMDEV-431: --- Description: (was: [Stella PST to ost converter software|https://www.stelladatarecovery.com/ost-to-pst.html] is a great software that converts all data from ost files to a pst file. It can convert all unmounted and corrupted ost data files into the office365 account. Stella ost to PST converter software can [convert deleted information into pst files|https://www.stelladatarecovery.com/ost-to-pst.html]. This software supports the entire 32bit and 64bit versions of the ost file. Stella ost converter to pst software can convert every ost mailbox item to a pst file. For more details, click this page [https://www.stelladatarecovery.com/ost-to-pst.html] !Titu39 OSTS OFFIC 365.jpg! ** ) > How does Stella converts ost to PST software functions? > --- > > Key: COMDEV-431 > URL: https://issues.apache.org/jira/browse/COMDEV-431 > Project: Community Development > Issue Type: New Feature >Reporter: denideniel >Priority: Major > Attachments: Titu39 OSTS OFFIC 365.jpg > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-431) invalid ticket
[ https://issues.apache.org/jira/browse/COMDEV-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated COMDEV-431: --- Summary: invalid ticket (was: How does Stella converts ost to PST software functions?) > invalid ticket > -- > > Key: COMDEV-431 > URL: https://issues.apache.org/jira/browse/COMDEV-431 > Project: Community Development > Issue Type: New Feature >Reporter: denideniel >Priority: Major > Attachments: Titu39 OSTS OFFIC 365.jpg > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Request: New Mailing List for Security-oriented community
Hi, On Mon, Sep 20, 2021 at 8:27 AM Mark J. Cox wrote: > ...I still like this living in the community project though, because the > likely outcome > of the discussion are collation of resources and practices and the right > place for them is in comdev... Same here, and a Special Interest Group homepage might be good as well, see https://wiki.apache.org/confluence/display/COMDEV/Special+Interests+Groups+hosted+by+the+comdev+PMC Those haven't happened so far due to lack of concrete interest, but making them happen is easy. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: community website fails branding checks
Hi Sebb, On Sat, Sep 11, 2021 at 3:40 PM sebb wrote: > The community website currently fails most branding checks: > https://github.com/apache/comdev-site .. you mean these tests, right? https://whimsy.apache.org/site/project/comdev -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Master branch in web site https://github.com/apache/comdev-site
Hi Craig, On Tue, Aug 31, 2021 at 9:10 PM Craig Russell wrote: > ...I think now would be a good time to consider changing the main branch name > from "master" to "main" If you or someone is ready to take responsibility for the change and any ripple effects that it might have (*) I am not opposed. Please also change https://github.com/apache/comdev-events-site if you do that as its setup is very similar to https://github.com/apache/comdev-site and should IMO remain similar. -Bertrand (*) hopefully there won't be any ripple effects in this case, such as automated builds failing due to wrong expectations, but you never know until you do it. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PROPOSAL] homepages + mailing lists for communities of interests
Hi, On Thu, Jun 24, 2021 at 4:03 PM Bertrand Delacretaz wrote: >... > https://cwiki.apache.org/confluence/display/COMDEV/Special+Interests+Groups+hosted+by+the+comdev+PMC > > Feedback is welcome, especially as there's still interest after all this > time... Sorry, that should have been "if" there's still interest after all this time... If nobody's interested at this time I'll let this sit, we can always create those homepages later once there's actual interest. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PROPOSAL] homepages + mailing lists for communities of interests
Hi, Sorry that I took so long to reply. On Thu, May 13, 2021 at 8:11 PM Javi Roman wrote: > ...To create a community of interest: > > 1. A particular ASF project must initiate the request for creation. > 2. To do this, the project must nominate two PMCs who will be responsible > for maintaining the page and overseeing the mailing list. Yes, that's how it's described at https://cwiki.apache.org/confluence/display/COMDEV/Special+Interests+Groups+hosted+by+the+comdev+PMC - asking for 3 PMC members actually. > ...If this is the case, then an ex-PPMC of a project removed from the > Incubator (as in my case), cannot initiate the request to create the > community, and cannot be part of the maintenance of the space nor moderate > the mailing list. Is this correct?... Yes, I think it's easier for this PMC in terms of oversight if we require the shepherds to be PMC members. But that doesn't prevent anyone from participating later, the homepage will be editable by supplying pull requests to https://github.com/apache/comdev-site and anyone can participate in the mailing lists. I hope that works for you! -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [PROPOSAL] homepages + mailing lists for communities of interests
Hi, On Mon, May 10, 2021 at 2:01 PM Bertrand Delacretaz wrote: > Following up on recent discussions I have created a proposal here: > https://cwiki.apache.org/confluence/display/COMDEV/Communities+of+Interests+hosted+by+the+comdev+PMC This has slipped through the cracks of my long todo list, but I have finally refined the proposal according to the comments in this thread, and renamed it to Special Interests Groups which is more common for such things: https://cwiki.apache.org/confluence/display/COMDEV/Special+Interests+Groups+hosted+by+the+comdev+PMC Feedback is welcome, especially as there's still interest after all this time. I'm planning to put it up for vote by the comdev PMC members once discussion is over. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: FYI, the community.a.o website wrongly serves the events.a.o content as I write this
On Mon, May 31, 2021 at 6:15 PM Bertrand Delacretaz wrote: > ..See https://issues.apache.org/jira/browse/INFRA-21936 for details. Fixed now, thanks to Daniel Gruno, https://github.com/apache/comdev-events-site/commit/e491a71de38685b5191d14c7ba901a7bd7637b89 -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
FYI, the community.a.o website wrongly serves the events.a.o content as I write this
Hi, See https://issues.apache.org/jira/browse/INFRA-21936 for details. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: ASF-wide community support files on GitHub
On Sat, May 1, 2021 at 6:02 PM Christopher wrote: > ...Initially, it could just include a `.github/CODE_OF_CONDUCT.md` file > that contains the same content as > https://www.apache.org/foundation/policies/conduct ... Instead of copying that text I would prefer that CODE_OF_CONDUCT.md mentions that this repository belongs to a project of the Apache Software Foundation to which https://www.apache.org/foundation/policies/conduct applies. We tend to have too much duplicated information already. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[PROPOSAL] homepages + mailing lists for communities of interests
Hi, Following up on recent discussions I have created a proposal here: https://cwiki.apache.org/confluence/display/COMDEV/Communities+of+Interests+hosted+by+the+comdev+PMC Feedback is welcome and I'm planning to put it up for vote by the comdev PMC members once discussion is over, ideally next Monday. The gist of it is: comdev offers a homepage under community.apache.org/c/ and a mailing list at @community.apache.org for communities of interests of ASF projects if they can provide 3 ASF Members to oversee those resources. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Comdev web pages for our communities of interests?
Hi, On Wed, May 5, 2021 at 12:10 AM Daniel Ruggeri wrote: > I am reminded that projects.apache.org has metadata classifications as well. > Perhaps using that data more effectively could be another option? .. I think projects.a.o is really about metadata - it could include links to a project's communities of interests once those are created, but for the communities homepages I think community.apache.org/c/ is better, especially as it's very easy to manage. I have now prepared a proposal on the wiki, will point to it in a new thread. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Comdev web pages for our communities of interests?
On Mon, May 10, 2021 at 11:16 AM Greg Stein wrote: > ...Also please note that a mailing list named healthc...@apache.org was > requested. Infra has deleted that request. Please keep requests within > the @community space... I assume by "within the @community space" you mean that healthc...@community.apache.org is ok, assuming oversight by the comdev PMC. ( and we can create that ourselves via https://selfserve.apache.org/mail.html ) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Update to How it Works for developers/contributors
Hi, On Sun, May 9, 2021 at 2:58 AM Craig Russell wrote: > ...So perhaps we could add a section on "contributors" that covers the other > categories of non-developer contributors?.. Note that the "developer" section at [1] already says "A developer is a user who contributes to a project in the form of code or documentation." so I think it can just be extended with a note that mentions other types of contributions besides code and documentation. And maybe also in the committer section mention that it's not necessarily about committing code but also being "committed" to the project by making other forms of contributions. Although the vast majority of our committers do write code, those who don't are not "second-class citizens". > ...2. I believe that we should ask contributors for an ICLA long before they > are invited to become committers... If you want to make that recommendation I think it belongs to https://www.apache.org/dev/pmc.html - that's a PMC concern, not directly related to how we work. -Bertrand [1] https://www.apache.org/foundation/how-it-works.html - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Update to ICLA to include github id
On Sun, May 9, 2021 at 5:47 AM Justin Mclean wrote: > ...Since recent projects trend to use GitHub and GitHub names instead of real > names. It can make it hard to match ICLAs to real people so I think it > makes sense to have it on the ICLA form. Best to probably make it optional > as not everyone have a GitHub account... I agree that an optional GitHub username field might be useful but IMO making it optional is a MUST. Requiring someone to have a GitHub account before they can get an Apache ID would be very wrong. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Brackets an Adobe Project.
Hi, On Sat, May 1, 2021 at 10:04 PM Kerry Voss wrote: > ...I am looking at Apache to adopt the Brackets > Project and think it would be a good fit for your organization... Note that the ASF doesn't have a technical strategy, on purpose, as we "just" provide space for our projects to flourish. So what the project does is not really relevant to incubating at the ASF. As Andrew mentioned, the first step for a project to join the ASF is to prepare an incubation proposal, see https://incubator.apache.org/cookbook/ for how that works. The ASF cannot "adopt" code without explicit permission from whoever owns that code, so besides an initial community a Software License Grant would be needed, as per https://www.apache.org/licenses/contributor-agreements.html I see at https://github.com/adobe/brackets that Adobe is encouraging people to fork on GitHub if they want to continue developing the software. That's cool, but I don't think that's sufficient for the ASF to adopt that code, an explicit donation of the code to the ASF would be needed. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: ASF and Healthcare initiative
Hi, On Thu, Apr 29, 2021 at 7:45 AM Javi Roman wrote: > ...This project/initiative could be a site (healthcare.apache.org and a > mailing list healthc...@apache.org) I thought about this again and it might make sense to generalize and provide space for such webpages under community.apache.org/c, see the "Comdev web pages for our communities of interests" thread that I just started on this list. That would be for a homepage for such an initiative, and a mailing list can be created by any of the PMCs involved in the initiative via https://selfserve.apache.org/ and listed on that homepage. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Comdev web pages for our communities of interests?
Hi, Recent discussions around a website for our projects which are in the healthcare "space" make me think that it would be useful to provide a space for such "project groups" which share common goals. How about providing web pages, under the oversight of the Comdev PMC, for such things? We could have community.apache.org/c/healthcare, community.apache.org/c/osgi, community.apache.org/c/buildtools, etc., reserving community.apache.org/c as the root for that (as in "communities"). Our website is very easy to manage, see https://github.com/apache/comdev-site, it should be easy for interested people to provide pull requests for those pages. The advantage compared to individual websites such as healthcare.apache.org (as discussed in another thread here) is that it's very easy to create a new page under community.apache.org/c and the Comdev PMC stays in charge in case such pages become stale or orphaned over time. These communities can then request other resources such as mailing lists if desired, using https://selfserve.apache.org/ in most cases, those pages are only meant to be used as homepages, with a description of the corresponding community and links to the interested projects and other places of interest. What do people think? -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
