I agree with Robert – localization (this is what we do at MotaWord) is a maintenance work. If not maintained as well as mainstream, it will only damage and distant devs that use those local websites.
Re: comments, I don't think people will really discuss furiously. But we at least need a system where we understand the popularity of a package, it helps to pick among similar packages if any. Something like the popularity figure here that we can fetch from somewhere: https://mvnrepository.com/popular --- Oytun Tez *M O T A W O R D* The World's Fastest Human Translation Platform. oy...@motaword.com — www.motaword.com On Tue, Jul 23, 2019 at 5:07 AM Robert Metzger <rmetz...@apache.org> wrote: > Thanks a lot Marta for offering to write a blog post about the community > site! > > I'm not sure if multi-language support for the site is a good idea. I see > the packages site as something similar to GitHub or Jira. The page itself > contains very view things we could actually translate. The package owners > usually are only able to provide one or two languages for their package > description. > For the comments, we don't want disjoint discussions to happen. > > I've also kicked off a discussion with Apache legal on the initiative [1]. > We might not be able to host this at Apache, but let's see where the > discussion goes. > > > [1] > https://lists.apache.org/thread.html/ee76a02257b51292ab61f6ac8d3d69307e83cc569cdeebde80596207@%3Clegal-discuss.apache.org%3E > > > On Sat, Jul 20, 2019 at 5:25 AM Becket Qin <becket....@gmail.com> wrote: > >> [Sorry for the incomplete message. Clicked send by mistake...] >> >> I agree with Marta that it might be good to have multi-language support >> as a mid-term goal. >> >> Jiangjie (Becket) Qin >> >> On Sat, Jul 20, 2019 at 11:22 AM Becket Qin <becket....@gmail.com> wrote: >> >>> The website is awesome! I really like its conciseness and yet fairly >>> useful information and functionalities. I cannot think of much to improve >>> at the moment. Just one thought, do we need an "others" category, just in >>> case a package does not fit into any of the current given categories? >>> >>> Thanks Robert and Daryl for the great effort. Looking forward to seeing >>> this get published soon!! >>> >>> I agree with Marta that >>> >>> Jiangjie (Becket) Qin >>> >>> On Sat, Jul 20, 2019 at 1:34 AM Marta Paes Moreira <ma...@ververica.com> >>> wrote: >>> >>>> Hey, Robert. >>>> >>>> I will keep an eye on the overall progress and get started on the blog >>>> post >>>> to make the community announcement. Are there (mid-term) plans to >>>> translate/localize this website as well? It might be a point worth >>>> mentioning in the blogpost. >>>> >>>> Hats off to you and Daryl — this turned out amazing! >>>> >>>> Marta >>>> >>>> On Thu, Jul 18, 2019 at 10:57 AM Congxian Qiu <qcx978132...@gmail.com> >>>> wrote: >>>> >>>> > 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. >>>> >>>>>>> >>>> >>>>>>> >>>> >>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>> >>>> >>>
