from mobile (sorry for typos ;)

On Mon, Mar 14, 2022, 17:11 Gilles Sadowski <gillese...@gmail.com> wrote:

> Hi.
>
> Le lun. 14 mars 2022 à 10:56, Maxim Solodovnik <solomax...@gmail.com> a
> écrit :
> >
> > Sorry for top-posting
> > COMDEV JIRA is being used by the projects which don't use JIRA as tracker
> > ....
> >
>
> I'm not sure how this answers my question(s).
> Should I proceed with INFRA-22893 as if it were a "Commons"-specific
> request?
> Having tasks listed in the COMDEV would be more flexible, efficient and
> consistent than the "GSoC 2022 Ideas list".
>

Sorry
It seems I didn't got the question :(
The fields are common for all ASF projects
But
Every project participating in GSoC might want to have them

Some ASF projects do not use JIRA. These projects uses COMDEV JIRA to file
GSoC ideas

Hope I was able to describe everything :)


> Regards,
> Gilles
>
> >
> >
> > On Mon, Mar 14, 2022, 16:28 Gilles Sadowski <gillese...@gmail.com>
> wrote:
> >
> > > Hello.
> > >
> > > Le lun. 14 mars 2022 à 08:16, Maxim Solodovnik <solomax...@gmail.com>
> a
> > > écrit :
> > > >
> > > > I get no objections so far
> > > > So I'll create JIRA to add these fields for COMDEV :)
> > >
> > > Do you mean to create another JIRA?
> > >
> > > What about this one:
> > >   https://issues.apache.org/jira/browse/INFRA-22893
> > > ?
> > >
> > > Perhaps it will indeed be clearer if we create (in effect: duplicate)
> > > reports in the "COMDEV" JIRA project[1] and link them to the
> > > corresponding task in the specific TLP JIRA project.
> > > The COMDEV JIRA would hold the "administrative" fields (thus they
> > > don't have to be added to the any other TLP).  [Same for the "gsoc"
> > > tags.]
> > >
> > > WDYT?
> > >
> > > Gilles
> > >
> > > [1] There are indeed several old GSoC-related issues there:
> > >        https://issues.apache.org/jira/projects/COMDEV
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Reply via email to