Bug#824912: tracker.d.o: add an API for action items
Hi,
On Tue, 13 Dec 2016, efkin wrote:
> so my next questions are:
>
> * should we create a dedicated app for the API (called "api")?
No opinion. I guess it depends if we want to make the API optional
in the deployment.
> * should we change the title of the issue or take it as it is and use it
> as an snowpiercer for the API development?
I would say that #756028 would likely be the best place to discuss the API
in general.
> * is it better to discuss these things on irc and then copy-paste on this
> thread?
If we discuss on IRC it's always good to make a summary by email, yes.
Then it's also possible to have the whole conversation over email.
> * i saw that the actual view design patterns are to use mainly CBV,
> should we go for coherence with this pattern in the API?
Use whatever works best for the task at hand. CBV are fine in general.
> * as this task can take some commits, is it okay to clone in my gitlab
> acocunt and then choose from there relevant commits or can i have push
> access to a specific branch or is it just okay for the QA Team to
> handle patches by email?
If you contribute regularly, I would certainly welcome if you had
your own repository that I can merge from. That said I like to
have patches by email so that I can review and comment just by
reading and responding.
You could have access to the repository on alioth.debian.org,
but you would need to join the qa project. I'm not opposed to that
but I would rather wait until you have contributed a bit more
and until I know you a bit more as well.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
Reply to: