What still makes me feel most comfortable with the plug-in--centered
tasks proposal is that it doesn't try to conceal what actually happens
behind the scenes: a plug-in specific task code is fired all the time
a new repository version is created, that uses multiple (generic) core
Pulp objects to wo
Here is where I stand:
-1 on converting the task status API to task creation API (the original
proposal)
+1 on adding a hook for plugins to provide repository version validation of
content
+1 on exploring other ideas to make the v3 API more RESTful (removing the
action end points such as 'sync' an
I updated the MVP doc with the changes[0] we discussed on the list and
during a call we had earlier today. Below are the notes I captured during
the call.
- remove default remote for a repository feature
- we are not implementing auto publish feature
- create an issue for removing auto_publish
In the MVP document, we have several filtering user stories that call out
an id_in_list filter. During our sprint planning, there was a suggestion to
leave this out until after the MVP. I think one of the main users of this
filter will be Katello and we’re not planning on supporting them in the MVP
I’ve had a chance to think about this some more this week and reread all
the emails. I think that the solution of just adding a hook is best. Each
solution seems to be imperfect and I think we still want users to interact
with objects (remotes, repositories, etc). I’d say I’m +1 on adding a hook
an
On Tue, Apr 3, 2018 at 3:47 PM, Austin Macdonald wrote:
> Interesting proposals Milan!
>
> I am forking Brian's email so that thread can focus on communication,
> redmine, etc.
Thanks, I guess it would best go hand-in-hand with the process update
proposal for the Technical specifications/blue-pri
Interesting proposals Milan!
I am forking Brian's email so that thread can focus on communication,
redmine, etc.
On Tue, Apr 3, 2018 at 8:13 AM, Milan Kovacik wrote:
> I'd also like to propose formal Project Technical Lead and a formal
> Project Community Lead roles to be able to decide in case
I'd also like to propose formal Project Technical Lead and a formal
Project Community Lead roles to be able to decide in case of competing
(technical) ideas or planning priorities.
These would have to be time-boxed (half a year) and folks would elect
the leader for a period based on leader's progra
