I support the move and I think we should do it as soon as possible. If there is anything I can do to support, let me know.
Donat On Sat, Jan 5, 2019 at 12:26 AM Mike Percy <mpe...@apache.org> wrote: > > Hi Ferenc, OK sounds good. Let me know if you want help looking at any of > the web site issues. > > I agree that the gitbox site update should be done separately to avoid > impacting the release and for ease of managing the changes. > > I'm happy to create the INFRA ticket when the time comes, or if you want to > do it that's fine with me as well. It seems to me that unless we hear > differently from someone else in the next day or so, we have lazy consensus > on asking ASF Infra to move Flume to gitbox after the 1.9.0 release. > > Mike > > > > > On Thu, Jan 3, 2019 at 4:33 PM Ferenc Szabo <szabofe...@apache.org> wrote: > > > Hi Mike, > > > > +1 from me to the gitbox migration. > > > > > > > > I am currently working on the website update. I just want to carefully > > check the whole site to fix dead links and wrong asset URLs that are > > present on the current deployed site. > > It will be done soon. After that, I am going to do the announcement and I > > have already planned to handle the gitbox migration. > > I would like to do it in a separate site update so the two updates do not > > hold back each other. It is not a big change. > > > > > > When we have a consensus here on this thread then I can create the JIRA > > ticket. > > > > > > Regards, > > Ferenc > > > > > > > > > > > > On Thu, Jan 3, 2019 at 6:38 PM Mike Percy <mpe...@apache.org> wrote: > > > > > Hi Flume devs, > > > I propose we ask ASF Infra to move the Flume Git repo to GitBox as soon > > as > > > the release has been finalized / announced. Once they switch things over, > > > we can update the web site / documentation to reflect that. > > > > > > Does anyone see any problems with this approach? > > > > > > Ferenc, when do you expect to announce the release and push the updated > > > site / docs? We can coordinate the date with infra@ based on that. > > > > > > Thanks, > > > Mike > > > > > > > > > On Thu, Jan 3, 2019 at 5:19 AM Apache Infrastructure Team < > > > infrastruct...@apache.org> wrote: > > > > > > > Hello, flume folks. > > > > As stated earlier in 2018, all git repositories must be migrated from > > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old service > > > > is being decommissioned. Your project is receiving this email because > > > > you still have repositories on git-wip-us that needs to be migrated. > > > > > > > > The following repositories on git-wip-us belong to your project: > > > > - flume.git > > > > > > > > > > > > We are now entering the mandated (coordinated) move stage of the > > roadmap, > > > > and you are asked to please coordinate migration with the Apache > > > > Infrastructure Team before February 7th. All repositories not migrated > > > > on February 7th will be mass migrated without warning, and we'd > > > appreciate > > > > it if we could work together to avoid a big mess that day :-). > > > > > > > > Moving to gitbox means you will get full write access on GitHub as > > well, > > > > and be able to close/merge pull requests and much more. > > > > > > > > To have your repositories moved, please follow these steps: > > > > > > > > - Ensure consensus on the move (a link to a lists.apache.org thread > > will > > > > suffice for us as evidence). > > > > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA > > > > > > > > Your migration should only take a few minutes. If you wish to migrate > > > > at a specific time of day or date, please do let us know in the ticket. > > > > > > > > As always, we appreciate your understanding and patience as we move > > > > things around and work to provide better services and features for > > > > the Apache Family. > > > > > > > > Should you wish to contact us with feedback or questions, please do so > > > > at: us...@infra.apache.org. > > > > > > > > > > > > With regards, > > > > Apache Infrastructure > > > > > > > > > > > > >
