Robert and Daryl, thanks for the great work, I tried the website and filed some issues on Github. Best, Congxian
Robert Metzger <rmetz...@apache.org> 于2019年7月17日周三 下午11:28写道： > Hey all, > > Daryl and I have great news to share. We are about to finish adding the > basic features to the ecosystem page. > We are at a stage where it is ready to be reviewed and made public. > > You can either check out a development instance of the ecosystem page > here: https://flink-ecosystem-demo.flink-resources.org/ > Or you run it locally, with the instructions from the README.md: > https://github.com/sorahn/flink-ecosystem > > Please report all issues you find here: > https://github.com/sorahn/flink-ecosystem/issues or in this thread. > > The next steps in this project are the following: > - We fix all issues reported through this testing > - We set up the site on the INFRA resources Becket has secured [1], do > some further testing (including email notifications) and pre-fill the page > with some packages. > - We set up a packages.flink.apache.org or flink.apache.org/packages > domain > - We announce the packages through a short blog post > > Happy testing! > > Best, > Robert > > [1] https://issues.apache.org/jira/browse/INFRA-18010 > > > On Thu, Apr 25, 2019 at 6:23 AM Becket Qin <becket....@gmail.com> wrote: > >> Thanks for the update, Robert. Looking forward to the website. If there >> is already a list of software we need to run the website, we can ask Apache >> infra team to prepare the VM for us, as that may also take some time. >> >> On Wed, Apr 24, 2019 at 11:57 PM Robert Metzger <rmetz...@apache.org> >> wrote: >> >>> Hey all, >>> >>> quick update on this project: The frontend and backend code have been >>> put together into this repository: >>> https://github.com/sorahn/flink-ecosystem >>> We also just agreed on an API specification, and will now work on >>> finishing the backend. >>> >>> It will probably take a few more weeks for this to finish, but we are >>> making progress :) >>> >>> Best, >>> Robert >>> >>> >>> On Mon, Apr 15, 2019 at 11:18 AM Robert Metzger <rmetz...@apache.org> >>> wrote: >>> >>>> Hey Daryl, >>>> >>>> thanks a lot for posting a link to this first prototype on the mailing >>>> list! I really like it! >>>> >>>> Becket: Our plan forward is that Congxian is implementing the backend >>>> for the website. He has already started with the work, but needs at least >>>> one more week. >>>> >>>> >>>> [Re-sending this email because the first one was blocked on dev@f.a.o] >>>> >>>> >>>> On Mon, Apr 15, 2019 at 7:59 AM Becket Qin <becket....@gmail.com> >>>> wrote: >>>> >>>>> Hi Daryl, >>>>> >>>>> Thanks a lot for the update. The site looks awesome! This is a great >>>>> progress. I really like the conciseness of GUI. >>>>> >>>>> One minor suggestion is that for the same library, there might be >>>>> multiple versions compatible with different Flink versions. It would be >>>>> good to show that somewhere in the project page as it seems important to >>>>> the users. >>>>> >>>>> BTW, will you share the plan to move forward? Would additional hands >>>>> help? >>>>> >>>>> Thanks, >>>>> >>>>> Jiangjie (Becket) Qin >>>>> >>>>> On Sat, Apr 13, 2019 at 7:10 PM Daryl Roberts <da...@ververica.com> >>>>> wrote: >>>>> >>>>>> > Shall we add a guide page to show people how to publish their >>>>>> projects to the website? The exact rules can be discussed and drafted in >>>>>> a >>>>>> separate email thread IMO >>>>>> >>>>>> This is a good idea. (Both the guise, and separate thread), I think >>>>>> once there is an actual packed in place we’ll be in a lot better position >>>>>> to discuss this. >>>>>> >>>>>> > The "Log in with Github" link doesn't seem to work yet. Will it >>>>>> only allow login for admins and publishers, or for everyone? >>>>>> >>>>>> Correct, all the oauth stuff requires a real server. We are currently >>>>>> just faking everything. >>>>>> >>>>>> I will add a mock-login page (username/password that just accepts >>>>>> anything and displays whatever username you type in) so we can see the >>>>>> add-comment field and add-packages page once they exist. >>>>>> >>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>
