[jira] [Commented] (INCUBATOR-269) Podlings Guides menu is too long and does not scroll
[ https://issues.apache.org/jira/browse/INCUBATOR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395151#comment-17395151 ] Bertrand Delacretaz commented on INCUBATOR-269: --- I think an index page is simple to create and it also allows for creating categories, commenting the suggested reading sequence etc. > Podlings Guides menu is too long and does not scroll > > > Key: INCUBATOR-269 > URL: https://issues.apache.org/jira/browse/INCUBATOR-269 > Project: Incubator > Issue Type: Task > Components: UX >Reporter: Dave Fisher >Priority: Major > > There are 20 menus and many dividers on the podling guides menu. > I suggest a different approach is needed. > Options: > # Create guides/index.ad and have an outline of the guides on that page. > # Have a submenu structure. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-266) Update the website redirect page of weex
[ https://issues.apache.org/jira/browse/INCUBATOR-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358618#comment-17358618 ] Bertrand Delacretaz commented on INCUBATOR-266: --- In the meantime I found the new README at [https://github.com/apache/incubator/blob/master/assets/retired/README.md] which clarifies this, thank you. > Update the website redirect page of weex > > > Key: INCUBATOR-266 > URL: https://issues.apache.org/jira/browse/INCUBATOR-266 > Project: Incubator > Issue Type: Task >Reporter: Willem Jiang >Priority: Major > > We can create an empty index.html for the retired project to redirect the > page to incubator project status page. > Here are the more information about in the mailing list. > https://lists.apache.org/thread.html/r361999f665b90434c285161925935f3da759c6f95d6959763860f4f2%40%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-266) Update the website redirect page of weex
[ https://issues.apache.org/jira/browse/INCUBATOR-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358600#comment-17358600 ] Bertrand Delacretaz commented on INCUBATOR-266: --- Thank you for this, to make sure I understand, could someone clarify this statement from the above dev list thread: bq. The web server that hosts all the podling websites checks for a directory matching the host name, and redirects to the podling status file if it is present. Do I understand correctly that the goal is to redirect http://weex.apache.org to https://incubator.apache.org/projects/weex.html ? (which is what is happening now - I just want to make sure we document this clearly as those nice "minor bits of magic" are often hard to follow when we look at this again in the future) RTFM links welcome of course. > Update the website redirect page of weex > > > Key: INCUBATOR-266 > URL: https://issues.apache.org/jira/browse/INCUBATOR-266 > Project: Incubator > Issue Type: Task >Reporter: Willem Jiang >Priority: Major > > We can create an empty index.html for the retired project to redirect the > page to incubator project status page. > Here are the more information about in the mailing list. > https://lists.apache.org/thread.html/r361999f665b90434c285161925935f3da759c6f95d6959763860f4f2%40%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing
[
https://issues.apache.org/jira/browse/INCUBATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041748#comment-17041748
]
Bertrand Delacretaz commented on INCUBATOR-250:
---
Thank you! It would be good to improve error reporting but for now the build
works indeed.
> Website build (part 1 - Clutch phase) failing
> -
>
> Key: INCUBATOR-250
> URL: https://issues.apache.org/jira/browse/INCUBATOR-250
> Project: Incubator
> Issue Type: Bug
>Reporter: Bertrand Delacretaz
>Assignee: Dave Fisher
>Priority: Major
>
> Recent builds are failing at
> https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
> so things like IP clearance forms are not updated on the website.
> I tried running {{sh build_local_clutch.sh}} from
> https://github.com/apache/incubator on my laptop and this gives the following
> error:
> {code}
>
> STATUS: podlings: 44
> Build Clutch Status Pages
> STATUS: pages: 44
> ABORT: clutch2.sh error
> {code}
> I don't know this code so can't tell what's happening from those messages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing
[
https://issues.apache.org/jira/browse/INCUBATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041095#comment-17041095
]
Bertrand Delacretaz commented on INCUBATOR-250:
---
The content of https://github.com/apache/incubator hasn't changed in the last
28 days so I suppose it's a change in svn that's causing problems,
https://svn.apache.org/repos/asf/incubator/public/trunk
> Website build (part 1 - Clutch phase) failing
> -
>
> Key: INCUBATOR-250
> URL: https://issues.apache.org/jira/browse/INCUBATOR-250
> Project: Incubator
> Issue Type: Bug
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> Recent builds are failing at
> https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
> so things like IP clearance forms are not updated on the website.
> I tried running {{sh build_local_clutch.sh}} from
> https://github.com/apache/incubator on my laptop and this gives the following
> error:
> {code}
>
> STATUS: podlings: 44
> Build Clutch Status Pages
> STATUS: pages: 44
> ABORT: clutch2.sh error
> {code}
> I don't know this code so can't tell what's happening from those messages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing
[
https://issues.apache.org/jira/browse/INCUBATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated INCUBATOR-250:
--
Description:
Recent builds are failing at
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
so things like IP clearance forms are not updated on the website.
I tried running {{sh build_local_clutch.sh}} from
https://github.com/apache/incubator on my laptop and this gives the following
error:
{code}
STATUS: podlings: 44
Build Clutch Status Pages
STATUS: pages: 44
ABORT: clutch2.sh error
{code}
I don't know this code so can't tell what's happening from those messages.
was:
Recent builds are failing at
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
so things like IP clearance forms are not updated on the website.
I tried running {{sh build_local_clutch.sh}} from
https://github.com/apache/incubator on my laptop and this gives the following
error:
{code}
STATUS: podlings: 44
Build Clutch Status Pages
STATUS: pages: 44
ABORT: clutch2.sh error
{code}
I don't know this code so can't tell what's happening from those messages.
Interestingly, it looks like the last build that worked (#377) ran on the
current HEAD revision (d301ce36) so I really don't know what changed.
> Website build (part 1 - Clutch phase) failing
> -
>
> Key: INCUBATOR-250
> URL: https://issues.apache.org/jira/browse/INCUBATOR-250
> Project: Incubator
> Issue Type: Bug
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> Recent builds are failing at
> https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
> so things like IP clearance forms are not updated on the website.
> I tried running {{sh build_local_clutch.sh}} from
> https://github.com/apache/incubator on my laptop and this gives the following
> error:
> {code}
>
> STATUS: podlings: 44
> Build Clutch Status Pages
> STATUS: pages: 44
> ABORT: clutch2.sh error
> {code}
> I don't know this code so can't tell what's happening from those messages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-250) Website build (part 1 - Clutch phase) failing
Bertrand Delacretaz created INCUBATOR-250:
-
Summary: Website build (part 1 - Clutch phase) failing
Key: INCUBATOR-250
URL: https://issues.apache.org/jira/browse/INCUBATOR-250
Project: Incubator
Issue Type: Bug
Reporter: Bertrand Delacretaz
Recent builds are failing at
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
so things like IP clearance forms are not updated on the website.
I tried running {{sh build_local_clutch.sh}} from
https://github.com/apache/incubator on my laptop and this gives the following
error:
{code}
STATUS: podlings: 44
Build Clutch Status Pages
STATUS: pages: 44
ABORT: clutch2.sh error
{code}
I don't know this code so can't tell what's happening from those messages.
Interestingly, it looks like the last build that worked (#377) ran on the
current HEAD revision (d301ce36) so I really don't know what changed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-248) Incubation Overview page not found (404 error)
[ https://issues.apache.org/jira/browse/INCUBATOR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000851#comment-17000851 ] Bertrand Delacretaz commented on INCUBATOR-248: --- That part of the website is still maintained in svn, I have committed a fix to http://svn.apache.org/repos/asf/incubator/public/trunk/ that links to http://incubator.apache.org/cookbook/ instead of this dead link. The changes should be live within about an hour, probably less. > Incubation Overview page not found (404 error) > -- > > Key: INCUBATOR-248 > URL: https://issues.apache.org/jira/browse/INCUBATOR-248 > Project: Incubator > Issue Type: Bug >Reporter: Xiangdong Huang >Priority: Major > > The "incubation overview" page [1] on > incubator.apache.org/projects/PROJECT_NAME.html returns 404 error. > > "Incubator Overview" locates on the left side bar of a project's incubator > status page. > > I checked the error exists (maybe) on all incubator projects, e.g., IoTDB [2] > and ShardingSphere[3]. > > Does someone know how to fix it? > > [1] http://incubator.apache.org/policy/process.html > [2] [http://incubator.apache.org/projects/iotdb.html] > [3] [http://incubator.apache.org/projects/shardingsphere.html] > [4] https://issues.apache.org/jira/browse/INFRA-19597 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814129#comment-16814129 ] Bertrand Delacretaz commented on INCUBATOR-234: --- I like these but now we have to decide whether everything belongs in the cookbook, or if we should rather keep it a the overview / principles level and have the details in the guides. I think I prefer the latter (though the guides need cleaning up as well): it allows people to read the cookbook in one sitting and get lots of useful information without too many details. Or maybe go back to building the cookbook out of multiple smaller files (like before [https://github.com/apache/incubator/commit/20c6621b], and have two sections, main and appendix, in those files. Display the main sections only in the cookbook, with a link to the full info including appendix - that might be provide the most consistent view. > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/ , > |http://incubator.apache.org/cookbook/]source > [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] > h2. How to contribute to this effort > * Feedback and suggestions are welcome here. > * Pull requests at [https://github.com/apache/incubator] also work > * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] > list, [https://lists.apache.org/list.html?general@incubator.apache.org] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814126#comment-16814126 ] Bertrand Delacretaz commented on INCUBATOR-231: --- Very cool - maybe just ask on incubator@ and/or the Whimsy team if anyone's aware of this data being used elsewhere. And if you have info on where data is used it'd be good to document that along the way. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809682#comment-16809682 ] Bertrand Delacretaz commented on INCUBATOR-231: --- Thanks Dave, your changes work for me. +1 for a CLUTCH.md, and we might just keep a warning about clutch and a link to that page in the README. How about moving the clutch data links to http://incubator.apache.org/clutch/ and adding a link to CLUTCH.md there? That URL then becomes the "all you need to know about clutch" one. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808487#comment-16808487 ] Bertrand Delacretaz commented on INCUBATOR-231: --- Thank you very much for this Dave! I have updated the https://github.com/apache/incubator README accordingly, please cross-check. Giving that URL to someone should provide all the info they need to edit and publish the website. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[
https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807665#comment-16807665
]
Bertrand Delacretaz commented on INCUBATOR-234:
---
I agree with a page specific to Incubator PMC members, maybe use a different
name ("PMC page") to avoid confusion with "the cookbook". This should also
allow for simplifying the guides.
Also agree about the menu changes, once we get there.
> Incubator Cookbook
> --
>
> Key: INCUBATOR-234
> URL: https://issues.apache.org/jira/browse/INCUBATOR-234
> Project: Incubator
> Issue Type: Task
> Components: site
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> As discussed at [1] the goal is to create a single page Incubator Cookbook,
> with all the details of the incubation process, in chronological order of the
> incubation journey.
> This should be as concise as possible, with links to more information where
> strictly needed, and adopt a friendly tone in the sense of clearly making the
> Incubator a service to our podlings.
> Draft page at [http://incubator.apache.org/cookbook/ ,
> |http://incubator.apache.org/cookbook/]source
> [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad]
> As a next step I'll focus on getting a mostly consistent set of topics and we
> can then share the writing work.
> [1]
> [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E]
> h2. How to contribute to this effort
> * Feedback and suggestions are welcome here.
> * Pull requests at [https://github.com/apache/incubator] also work
> * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o]
> list, [https://lists.apache.org/list.html?general@incubator.apache.org]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807662#comment-16807662 ] Bertrand Delacretaz commented on INCUBATOR-231: --- I'm not sure if you can push to the master branch from a Jenkins build. But if not it's probably possible to push to raw clutch data to asf-site so it appears (unlinked) under incubator.apache.org/data and can be pulled from there by the main build. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806744#comment-16806744 ] Bertrand Delacretaz commented on INCUBATOR-234: --- Once we're happy with the contents of the cookbook I think the following pages can be removed. They have lots more detail but I don't thinks those are useful, except for a few exceptions which are noted. * http://incubator.apache.org/policy/incubation.html * http://incubator.apache.org/policy/process.html * http://incubator.apache.org/policy/roles_and_responsibilities.html (except "mentors", simplified, under "guides") * http://incubator.apache.org/podling-story.html * http://incubator.apache.org/guides/proposal.html (I think the cookbook, a template + the existing examples will do) * http://incubator.apache.org/guides/entry.html The idea is that the Incubator website structure would be: * The homepage with all the basic info (the "What are the steps to becoming an Apache Software Foundation Top-Level project?" that's now at http://incubator.apache.org/cookbook, pointers to mailing lists etc) * The cookbook as the next step, to get the overview and lots of basic information, at least for the "happy case" of the vast majority of podlings. * The guides (simplified and cleaned up) for more details * Links to other ASF general info as we have now * A cleaned-up FAQ So the policies, proposals, PMC guides disappear (the latter replaced by links to general ASF info), leaning on existing ASF documentation instead and just outlining the differences with podlings as done at http://incubator.apache.org/cookbook/#podling_top_level_project_what_are_the_differences For now these are just my ideas, I'm just thinking outloud here. Will bring this to our general@list for discussion once we feel good about the cookbook. > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/ , > |http://incubator.apache.org/cookbook/]source > [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] > h2. How to contribute to this effort > * Feedback and suggestions are welcome here. > * Pull requests at [https://github.com/apache/incubator] also work > * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] > list, [https://lists.apache.org/list.html?general@incubator.apache.org] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated INCUBATOR-234: -- Description: As discussed at [1] the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/ , |http://incubator.apache.org/cookbook/]source [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. [1] [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] h2. How to contribute to this effort * Feedback and suggestions are welcome here. * Pull requests at [https://github.com/apache/incubator] also work * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] list, [https://lists.apache.org/list.html?general@incubator.apache.org] was: As discussed at [1] the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. [1] [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] h2. How to contribute to this effort * Feedback and suggestions are welcome here. * Pull requests at [https://github.com/apache/incubator] also work * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] list, [https://lists.apache.org/list.html?general@incubator.apache.org] > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/ , > |http://incubator.apache.org/cookbook/]source > [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] > h2. How to contribute to this effort > * Feedback and suggestions are welcome here. > * Pull requests at [https://github.com/apache/incubator] also work > * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] > list, [https://lists.apache.org/list.html?general@incubator.apache.org] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated INCUBATOR-234: -- Description: As discussed at [1] the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] , built from small pieces of content found under [https://github.com/apache/incubator/tree/master/pages/cookbook] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. [1] [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] h2. How to contribute to this effort * Feedback and suggestions are welcome here. * Pull requests at [https://github.com/apache/incubator] also work * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] list, https://lists.apache.org/list.html?general@incubator.apache.org was: As discussed at [1] the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] , built from small pieces of content found under [https://github.com/apache/incubator/tree/master/pages/cookbook] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. [1] https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] > h2. How to contribute to this effort > * Feedback and suggestions are welcome here. > * Pull requests at [https://github.com/apache/incubator] also work > * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] > list, https://lists.apache.org/list.html?general@incubator.apache.org -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated INCUBATOR-234: -- Description: As discussed at [1] the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. [1] [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] h2. How to contribute to this effort * Feedback and suggestions are welcome here. * Pull requests at [https://github.com/apache/incubator] also work * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] list, [https://lists.apache.org/list.html?general@incubator.apache.org] was: As discussed at [1] the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] , built from small pieces of content found under [https://github.com/apache/incubator/tree/master/pages/cookbook] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. [1] [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] h2. How to contribute to this effort * Feedback and suggestions are welcome here. * Pull requests at [https://github.com/apache/incubator] also work * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] list, https://lists.apache.org/list.html?general@incubator.apache.org > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > [https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E] > h2. How to contribute to this effort > * Feedback and suggestions are welcome here. > * Pull requests at [https://github.com/apache/incubator] also work > * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] > list, [https://lists.apache.org/list.html?general@incubator.apache.org] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806609#comment-16806609 ] Bertrand Delacretaz commented on INCUBATOR-234: --- [~isa...@apache.org] I have reworked the "does my project fit" section in [https://github.com/apache/incubator/commit/87f25f9,] WDYT? > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806538#comment-16806538 ] Bertrand Delacretaz commented on INCUBATOR-234: --- In [https://github.com/apache/incubator/commit/20c6621] I have moved back to a single page for the cookbook, [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad] This gives us a table of contents + section links for free. bq. Release Distribution Policy is an important part to discuss within releases. The "Incubator Releases" section links to http://www.apache.org/legal/release-policy.html, do we need more than that? bq. How should exceptions to the normal course be handled in the cookbook? If we really really have to I'd say small notes at the end of each section? But in general I'd prefer the cookbook to describe the happy case, with details in the (simplified) http://incubator.apache.org/guides/ . So maybe the notes can just hints at possible differences and point to the guides for details? > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802756#comment-16802756 ] Bertrand Delacretaz commented on INCUBATOR-234: --- Another suggestion by Nick Kwiatkowski on Twitter ( https://twitter.com/quetwo/status/1110863303465684999 ) is to add a "differences between podlings and top-level projects" section about this: bq. Maybe better define PMC / PPMC? Maybe a section on "Who should be on the PPMC / what values should a PPMC have" and "What is the difference between a PPMC member and a committer?" > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802754#comment-16802754 ] Bertrand Delacretaz commented on INCUBATOR-234: --- Suggestion from [~isa...@apache.org] on Twitter: bq. What I would have found helpful in the "does your project fit the Apache Incubator" would have been a link of Apache's values so potential podlings can check if they match with what they want to aspire to. Maybe a link to https://blogs.apache.org/foundation/entry/the-apache-way-to-sustainable ? > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802642#comment-16802642 ] Bertrand Delacretaz commented on INCUBATOR-234: --- I have created an initial version at [http://incubator.apache.org/cookbook/] , covering (hopefully) all phases of incubation. There's a number of TODO, mostly about adding links to reference docs. I'm not sure if building this page out of multiple small documents is really useful but that's a detail, I suggest that for now we focus on the content and try to make this a central place for podling community members to find information and get an overview on how things work. Looking at the other incubator.a.o pages, a lot of information is presented as being specific to podlings - I'd rather point to the same docs as for top-level projects and just outline the small differences that apply to podlings, which works well in the context of that cookbook page. This should allow us to greatly simplify the rest of the website. > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-234) Incubator Cookbook
[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated INCUBATOR-234: -- Description: As discussed at [1] the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] , built from small pieces of content found under [https://github.com/apache/incubator/tree/master/pages/cookbook] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. [1] https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E was: As discussed at the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] , built from small pieces of content found under [https://github.com/apache/incubator/tree/master/pages/cookbook] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. > Incubator Cookbook > -- > > Key: INCUBATOR-234 > URL: https://issues.apache.org/jira/browse/INCUBATOR-234 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz >Priority: Major > > As discussed at [1] the goal is to create a single page Incubator Cookbook, > with all the details of the incubation process, in chronological order of the > incubation journey. > This should be as concise as possible, with links to more information where > strictly needed, and adopt a friendly tone in the sense of clearly making the > Incubator a service to our podlings. > Draft page at [http://incubator.apache.org/cookbook/] , built from small > pieces of content found under > [https://github.com/apache/incubator/tree/master/pages/cookbook] > As a next step I'll focus on getting a mostly consistent set of topics and we > can then share the writing work. > [1] > https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-234) Incubator Cookbook
Bertrand Delacretaz created INCUBATOR-234: - Summary: Incubator Cookbook Key: INCUBATOR-234 URL: https://issues.apache.org/jira/browse/INCUBATOR-234 Project: Incubator Issue Type: Task Components: site Reporter: Bertrand Delacretaz As discussed at the goal is to create a single page Incubator Cookbook, with all the details of the incubation process, in chronological order of the incubation journey. This should be as concise as possible, with links to more information where strictly needed, and adopt a friendly tone in the sense of clearly making the Incubator a service to our podlings. Draft page at [http://incubator.apache.org/cookbook/] , built from small pieces of content found under [https://github.com/apache/incubator/tree/master/pages/cookbook] As a next step I'll focus on getting a mostly consistent set of topics and we can then share the writing work. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801934#comment-16801934 ] Bertrand Delacretaz commented on INCUBATOR-231: --- bq. The clutch2.py scripting should be scheduled once a day instead of the git build The cleanest way to do that is probably to move the clutch-related content to its own repository? That would naturally decouple the build cycles of the main and clutch content. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794821#comment-16794821 ] Bertrand Delacretaz commented on INCUBATOR-231: --- If you need more Jenkins rights, a PMC chair needs to add you to https://whimsy.apache.org/roster/group/hudson-jobadmin - I canot do that myself. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Comment Edited] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794821#comment-16794821 ] Bertrand Delacretaz edited comment on INCUBATOR-231 at 3/18/19 8:08 AM: If you need more Jenkins rights, a PMC chair needs to add you to https://whimsy.apache.org/roster/group/hudson-jobadmin - I cannot do that myself. was (Author: bdelacretaz): If you need more Jenkins rights, a PMC chair needs to add you to https://whimsy.apache.org/roster/group/hudson-jobadmin - I canot do that myself. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, > clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, > gitbox.clutch.data.txt, gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16787734#comment-16787734
]
Bertrand Delacretaz commented on INCUBATOR-231:
---
Could we include some form of automated tests for the Clutch output? Maybe run
another script after {{clutch.py}} that checks a few well-known values from
{{clutch.pkl}} which IIUC is what drives other tools.
> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
> Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch2data.txt, gitbox.clutch.data.txt,
> gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from
> [https://github.com/apache/incubator] but a few things (clutch, project
> pages) are still maintained under
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders
> in svn that are not used anymore. Everything should move to Git to avoid
> confusion.
> Also, a lot of the projects information in the XML files found under
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is
> duplicated in other places, LDAP, podlings websites etc - it would be good to
> clean that up and simplify those pages to adapt to our current workflows,
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] ,
> not sure if that's used or useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785411#comment-16785411 ] Bertrand Delacretaz commented on INCUBATOR-231: --- bq. I am not sure if I agree on moving everything to git Ok, I agree that's the wrong focus, what I'm really after is streamlining the Incubator processes, cleaning up stale and irrelevant content and later streamline the website itself. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785410#comment-16785410 ] Bertrand Delacretaz commented on INCUBATOR-231: --- Taking alois as an example as Sebb mentioned it, it's good to have http://incubator.apache.org/projects/alois.html for historical purposes, but if you look at that page about 99.98% (ok, maybe a bit less) of it irrelevant, empty or out of date. I think the only information we need about past podlings is that they existed, what their description was, when they entered and exited the Incubator, and the URL where their code lives if we have it. Anything else can be found in our email archives if needed, as facts instead of stale copies of out of date information. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-231) Cleanup Git-generated Incubator website
Bertrand Delacretaz created INCUBATOR-231: - Summary: Cleanup Git-generated Incubator website Key: INCUBATOR-231 URL: https://issues.apache.org/jira/browse/INCUBATOR-231 Project: Incubator Issue Type: Task Reporter: Bertrand Delacretaz [http://incubator.apache.org/] is generated from [https://github.com/apache/incubator] but a few things (clutch, project pages) are still maintained under [http://svn.apache.org/repos/asf/incubator/public/trunk/] We should cleanup and unify for consistency, and there's a number of folders in svn that are not used anymore. Everything should move to Git to avoid confusion. Also, a lot of the projects information in the XML files found under [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is duplicated in other places, LDAP, podlings websites etc - it would be good to clean that up and simplify those pages to adapt to our current workflows, while preserving history where it makes sense. There are also YAML files with yet more duplicated information at [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693538#comment-16693538 ] Bertrand Delacretaz commented on INCUBATOR-222: --- Incubator PMC vote passed, http://incubator.apache.org/ip-clearance/openwhisk-composer.html updated with the vote links, all good now. > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690606#comment-16690606 ] Bertrand Delacretaz commented on INCUBATOR-222: --- IP clearance vote started at https://lists.apache.org/thread.html/4694c0831e47c6c2b17e3d1f3db80a209588532b8d2f25698186aad4@%3Cgeneral.incubator.apache.org%3E > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-226) IP Clearance for OpenWhisk Composer
Bertrand Delacretaz created INCUBATOR-226: - Summary: IP Clearance for OpenWhisk Composer Key: INCUBATOR-226 URL: https://issues.apache.org/jira/browse/INCUBATOR-226 Project: Incubator Issue Type: Task Reporter: Bertrand Delacretaz The donation of that module was discussed in INCUBATOR-222 and the IP clearance form has been created at http://incubator.apache.org/ip-clearance/openwhisk-composer.html but the Incubator PMC vote to accept the IP clearance has not happened. [~dgrove] before I start that vote, I have added a note to that IP clearance form stating that "as explained above, a Software Grant is not required, all contributors have an iCLA on file" Does that work for you? If yes I'll start the IP clearance vote. Sorry for the delay, this slipped through the cracks after the LEGAL-420 discussions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653428#comment-16653428 ] Bertrand Delacretaz commented on INCUBATOR-222: --- LEGAL-420 has started a discussion that will probably take some time to resolve. If all contributors are happy to proceed with just iCLAs (meaning that they have been delegated the right to grant a license to the ASF) I think we can proceed in good faith based on the current instructions. Otherwise, if you can get a Software Grant that's the safest option. I'm sorry that LEGAL-420 is slowing this down, but comments there have confirmed my impression that the current language is suboptimal. > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643593#comment-16643593 ] Bertrand Delacretaz commented on INCUBATOR-222: --- Ok thank you, we're good in terms of iCLAs then. I'm not totally convinced that a Software Grant is not needed in this case - Our IP clearance docs have changed in 2017 and I need a confirmation, created LEGAL-420 for that. Also, I see that the code has already been imported at [https://github.com/apache/incubator-openwhisk-composer] - that's not how it should have been, the IP clearance must happen before that in principle. Considering that this ticket should be closed soon I don't think that's a major problem, but we won't be able to release that module before this IP clearance is completed. I'll add a note to the README there. > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643472#comment-16643472 ] Bertrand Delacretaz commented on INCUBATOR-222: --- Website is fixed, the form is up at [http://incubator.apache.org/ip-clearance/openwhisk-composer.html] I see that you have set a date for "Check that all active committers have a signed CLA on record" but I didn't find all names in the roster at [https://whimsy.apache.org/roster/ppmc/openwhisk] - if I missed something, could you add the Apache IDs of those people after their names? Otherwise, if not all contributors to the donated software have an Apache iCLA on file, best is to file a Software Grant as per [https://www.apache.org/licenses/software-grant.txt] > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643209#comment-16643209 ] Bertrand Delacretaz commented on INCUBATOR-222: --- Thank you, https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-composer.xml is there indeed but the Incubator website deployment is currently failing, I have asked on the bui...@apache.org list about that, https://lists.apache.org/thread.html/1d362ca3367c5bb23f46db893b320f03ff5f18d1d4c819ad8749bcaa@%3Cbuilds.apache.org%3E > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16639868#comment-16639868 ] Bertrand Delacretaz commented on INCUBATOR-222: --- I'm helping another podling manage a similar IP clearance process in NETBEANS-1335 and it looks like podling committers can do everything themselves, would you agree to try that in this case? The instructions are at [http://incubator.apache.org/ip-clearance/] and the Incubator website instructions at [https://incubator.apache.org/guides/website.html] The first step is to create [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-ibm-composer.xml |https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/netbeans-mojohaus-utilities.xml]based on [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ip-clearance-template.xml] and fill out the fields for which you already have information. It's fine to have it on the incubator website before it's approved, as a work in progress. I'm happy to help with any aspects of this but I think it's useful if podling committers know how to do it, if you don't mind. You can list me as the ASF member managing the donation. > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-139) Apache Incubator Logo Contest 2016
[ https://issues.apache.org/jira/browse/INCUBATOR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768050#comment-15768050 ] Bertrand Delacretaz commented on INCUBATOR-139: --- Splendid - so I guess we can use a ticket like this one for the contest, put instructions in its description and we're good to go. > Apache Incubator Logo Contest 2016 > -- > > Key: INCUBATOR-139 > URL: https://issues.apache.org/jira/browse/INCUBATOR-139 > Project: Incubator > Issue Type: Task > Components: site >Reporter: Bertrand Delacretaz > Attachments: this-is-not-a-logo.jpg > > > Just checking out if this allows new jira users to upload their logos. If it > does we'll update this description with the contest information. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-139) Apache Incubator Logo Contest 2016
Bertrand Delacretaz created INCUBATOR-139: - Summary: Apache Incubator Logo Contest 2016 Key: INCUBATOR-139 URL: https://issues.apache.org/jira/browse/INCUBATOR-139 Project: Incubator Issue Type: Task Components: site Reporter: Bertrand Delacretaz Just checking out if this allows new jira users to upload their logos. If it does we'll update this description with the contest information. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (PODLINGNAMESEARCH-20) Establish whether Apache Clerezza is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13557105#comment-13557105 ] Bertrand Delacretaz commented on PODLINGNAMESEARCH-20: -- Looks good to me - Clerezza looks like a unique name to me, as confirmed by the above searches. Establish whether Apache Clerezza is a suitable name -- Key: PODLINGNAMESEARCH-20 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-20 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Tommaso Teofili A suitable name search is required in order for Clerezza to graduate from the incubation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (PODLINGNAMESEARCH-8) Establish whether Apache Stanbol is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411626#comment-13411626 ] Bertrand Delacretaz commented on PODLINGNAMESEARCH-8: - A media agency is sufficiently different from a software product that they can't be confused, I think it's fine to ignore that. Establish whether Apache Stanbol is a suitable name - Key: PODLINGNAMESEARCH-8 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-8 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Fabian Christ We have to do some investigations to ensure that Apache Stanbol is a suitable name for a TLP. People should start searching on the Web and add their findings as comments. We should state: * Evidence of the degree of open source adoption for the proposed name. * Evidence of trademark registrations for the proposed name. * Evidence of the degree of branding usage of the proposed name on the world wide web. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (PODLINGNAMESEARCH-8) Establish whether Apache Stanbol is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13411748#comment-13411748 ] Bertrand Delacretaz commented on PODLINGNAMESEARCH-8: - Please, please, please - no one is suggesting that the Stanbol name should change, this is just about due diligence w.r.t the current name. If a discussion about this is needed, please bring it to the dev list. Establish whether Apache Stanbol is a suitable name - Key: PODLINGNAMESEARCH-8 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-8 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Fabian Christ We have to do some investigations to ensure that Apache Stanbol is a suitable name for a TLP. People should start searching on the Web and add their findings as comments. We should state: * Evidence of the degree of open source adoption for the proposed name. * Evidence of trademark registrations for the proposed name. * Evidence of the degree of branding usage of the proposed name on the world wide web. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-82) Allow extra release distribution channels like the central Maven repository
[ https://issues.apache.org/jira/browse/INCUBATOR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628371#action_12628371 ] Bertrand Delacretaz commented on INCUBATOR-82: -- Looks good to me. Allow extra release distribution channels like the central Maven repository --- Key: INCUBATOR-82 URL: https://issues.apache.org/jira/browse/INCUBATOR-82 Project: Incubator Issue Type: Improvement Components: policy Reporter: Jukka Zitting Attachments: INCUBATOR-82.patch There has been a lot of discussion about whether to allow podlings to publish their releases in the central Maven repository. The current (undocumented) policy is that podlings may not use the central Maven repository as a distribution channel. I am planning to call the Incubator PMC to vote on changing this policy. Instead of the specific case of the Maven repository, I would like to make the policy change cover any _additional_ distribution channels that the podlings may want to use. Otherwise we'll be having the same discussion again with other channels like Ruby Gems, Python Package Index, Perl CPAN, etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611454#action_12611454 ] Bertrand Delacretaz commented on INCUBATOR-78: -- If we all agree that http://wiki.apache.org/incubator/ReportingSchedule is normative, basing the reminders on this page seems to be non-controversial. As recently missed report reminders show, projects are missing (or at least were missing) from that page - basing the list of projects on something more automated like svn repositories or a master file stored in svn sounds much safer and scalable. That wouldn't prevent creating report schedules by hand, but for the schedule to be reliable there needs IMHO to be an automated way of checking it against reference info, to make sure there are no phantom projects as is the case now. From memory, at least Pig, Rat and Bluesky have been forgotten in the reporting schedule, without anybody noticing for quite some time. Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610738#action_12610738 ] Bertrand Delacretaz commented on INCUBATOR-78: -- As a suggestion, each incubating project could have a status file at http://svn.apache.org/repos/asf/incubator/PROJECT/trunk/INCUBATOR-INFO.txt, where PROJECT is the project name. It's easy to verify with a script that this file is present, and putting it in the project's trunk makes it visible to and easily maintainable by the project community, as opposed to something that's stored away in incubator/trunk. The info might be something like: name: Buzzword description: Buzzword is a framework to create buzzword-compliant webapps in Java incubating-since: 2008-05-21 incubation-status: incubating mentors: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] reporting-months: May, June, July, October homepage: http://incubator.apache.org/buzzword committers-list: http://incubator.apache.org/buzzword/whoweare.html Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610816#action_12610816 ] Bertrand Delacretaz commented on INCUBATOR-78: -- With your proposal, if the svn:externals are not setup correctly, a project might be missing without it being noticed. The idea with http://svn.apache.org/repos/asf/incubator/PROJECT/trunk/INCUBATOR-INFO.txt is to use a recursive wget job, for example, which starts at http://svn.apache.org/repos/asf/incubator, visits all subfolders and checks for that file. In this case, as soon as a project has an svn repository there, the script can check its status file and complain if absent or incomplete - this would make it impossible for projects to be missed, as is the case now. Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610894#action_12610894 ] Bertrand Delacretaz commented on INCUBATOR-78: -- Do you know where the marvin code can be found? Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-78) Unreliable report schedule and list of podlings
Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-58) Sync whoweare.html with its source file
Sync whoweare.html with its source file --- Key: INCUBATOR-58 URL: https://issues.apache.org/jira/browse/INCUBATOR-58 Project: Incubator Issue Type: Improvement Reporter: Bertrand Delacretaz http://incubator.apache.org/whoweare.html is out of sync with the committee-info.txt source file. I'll update it, and change the order of names to use the same sort as in committee-info.txt (by first name), to make it easier to compare them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-58) Sync whoweare.html with its source file
[ https://issues.apache.org/jira/browse/INCUBATOR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489331 ] Bertrand Delacretaz commented on INCUBATOR-58: -- Here are the diffs on the sorted list of names, showing what has changed in revision 529518. The removal of Roy and Stefano looks ok according to these svn logs of committee-info.txt: Incubator PMC -= Roy T. Fielding 31JAN2007 r10368 | geirm | 2007-02-19 14:43:02 +0100 (Mon, 19 Feb 2007) | 2 lines Incubator PMC -= Stefano Mazzocchi r9644 | coar | 2006-11-13 18:35:43 +0100 (Mon, 13 Nov 2006) | 1 line here are the diffs: 2a3 Antoine Lévy-Lambert 5a7 Bertrand Delacrétaz 18a21 Eddie O'Neil 21a25 Gianugo Rabellino 26a31 Jason van Zyl 28a34 Jukka Zitting 33a40 Martin van den Bemt 34a42 Niclas Hedhman 40,41c48,49 Robert Burrell Donkin Roy T. Fielding --- Phil Steitz Robert Burrel Donkin 44c52,53 Stefano Mazzocchi --- Stefan Bodewig Stephane Bailliez I don't seem to have the Jira karma to close this issue, can someone do it? Sync whoweare.html with its source file --- Key: INCUBATOR-58 URL: https://issues.apache.org/jira/browse/INCUBATOR-58 Project: Incubator Issue Type: Improvement Reporter: Bertrand Delacretaz http://incubator.apache.org/whoweare.html is out of sync with the committee-info.txt source file. I'll update it, and change the order of names to use the same sort as in committee-info.txt (by first name), to make it easier to compare them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
