As far as I know Jan put in a ticket but we haven't heard back yet.

On Thu, Jun 15, 2017 at 10:18 AM, Chris Lemmons <[email protected]> wrote:

> I concur, as long as the github switch is happening in the fairly near
> future. The team has consensus on the switch, but have we let Apache
> Infrastructure know?
>
> On Mon, Jun 12, 2017 at 7:55 AM, Gelinas, Derek <[email protected]
> >
> wrote:
>
> > +1
> >
> > On Jun 12, 2017, at 9:54 AM, Dave Neuman <[email protected]<mailto:neum
> > [email protected]>> wrote:
> >
> > To be honest, I would hold off on that for now since we should be moving
> to
> > full github soon.
> > Once we move to full github we can slice and dice things up.
> >
> > On Sun, Jun 11, 2017 at 8:25 AM, Durfey, Ryan <[email protected]<
> > mailto:[email protected]>>
> > wrote:
> >
> > I wanted to start organizing the Jira issues and the first thing I need
> to
> > do is ensure components are assigned to each issue.  The list looks
> pretty
> > good, but I wanted to confirm a few before organizing?
> >
> >
> >  1.  Should we subdivide components like this?  If yes, are all of these
> > valid?
> >     *   Traffic Ops
> >     *   Traffic Ops API
> >     *   Traffic Ops ORT
> >     *   Traffic Ops Client
> >  2.  Should we have a component that relates back to Traffic Server to
> > indicate work that crosses over like "Traffic Server Related"?
> >  3.  Do we need generic components like these?
> >     *   Documentation
> >     *   Release
> >     *   All
> >  4.  All of these look good, any mods suggested?
> >     *   Traffic Analytics
> >     *   Traffic Logs
> >     *   Traffic Monitor
> >     *   Traffic Monitor (golang)
> >     *   Traffic Ops
> >     *   Traffic Portal
> >     *   Traffic Router
> >     *   Traffic Stats
> >     *   Traffic Vault
> >
> >
> > Ryan Durfey
> > Sr. Product Manager - CDN | Comcast Technology Solutions
> > 1899 Wynkoop Ste. 550 | Denver, CO 8020
> > M | 303-524-5099
> > [email protected]<mailto:[email protected]><mailto:
> > [email protected]>
> > CDN Support (24x7): 866-405-2993 or [email protected]<mailto:
> > [email protected]><mailto:
> > [email protected]<mailto:[email protected]>>
> >
> >
> >
>

Reply via email to