You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by "Sam Ruby (JIRA)" <ji...@apache.org> on 2019/04/10 17:27:00 UTC
[jira] [Comment Edited] (WHIMSY-110) Completion of a TLP resolution
should update podlings.xml
[ https://issues.apache.org/jira/browse/WHIMSY-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814685#comment-16814685 ]
Sam Ruby edited comment on WHIMSY-110 at 4/10/19 5:26 PM:
----------------------------------------------------------
The items that are done at the end of the board meeting can be found here: [https://github.com/apache/whimsy/blob/master/www/board/agenda/views/actions/todos.json.rb]
If you aren't fluent in Ruby, reading only the lines that start with a '#' in column one will give you a reasonable overview. What you will find is that the actions relate to the creation of a TLP, but with no current recognition that the incubator may have been involved in the practice.
Handling scenario 1 above would be straightforward. In most cases it would look something like
{noformat}
if ASF::Podling.find(name)
# update and commit podlings.xml
end{noformat}
Scenarios 2 and 3 will involve something either in addition or instead of this workflow. My suggestion would be to make changes to [https://whimsy.apache.org/roster/ppmc/] to allow mentors to note a pending name change (after which point, this scenario becomes identical to scenario 1 assuming that ASF::Podling.find knows about the new name) and to graduate into another PMC.
Making this happen will require changes to [https://github.com/apache/whimsy/tree/master/www/roster/views/ppmc] (which handles the client side) and [https://github.com/apache/whimsy/tree/master/www/roster/views/actions] (which handles the server side).
was (Author: rubys):
The items that are done at the end of the board meeting can be found here: [https://github.com/apache/whimsy/blob/master/www/board/agenda/views/actions/todos.json.rb]
If you aren't fluent in Ruby, reading only the lines that start with a '#' in column one will give you a reasonable overview. What you will find is that the actions relate to the creation of a TLP, but with no current recognition that the incubator may have been involved in the practice.
Handling scenario 1 above would be straightforward. In most cases it would look something like
{{if ASF::Podling.find(name)}}{{ # update and commit podlings.xml}}{{end}}
Scenarios 2 and 3 will involve something either in addition or instead of this workflow. My suggestion would be to make changes to [https://whimsy.apache.org/roster/ppmc/] to allow mentors to note a pending name change (after which point, this scenario becomes identical to scenario 1 assuming that ASF::Podling.find knows about the new name) and to graduate into another PMC.
Making this happen will require changes to [https://github.com/apache/whimsy/tree/master/www/roster/views/ppmc] (which handles the client side) and [https://github.com/apache/whimsy/tree/master/www/roster/views/actions] (which handles the server side).
> Completion of a TLP resolution should update podlings.xml
> ---------------------------------------------------------
>
> Key: WHIMSY-110
> URL: https://issues.apache.org/jira/browse/WHIMSY-110
> Project: Whimsy
> Issue Type: Improvement
> Reporter: John D. Ament
> Priority: Major
>
> When a podling graduates, via an Establish Foo resolution, we should update podlings.xml to indicate the graduated status of the project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)