Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Marc-Andre Roy
    @maroy1986
    no, I'm not refering to particular PRs, this is just a general observation, I fully understand some require more times to ensure everything is fine or can be categorized as nice to have
    bigopon
    @bigopon
    I see
    Marc-Andre Roy
    @maroy1986
    I'm trying to see it from the point of someone who's looking at aurelia to start and see all that, it might feels dead to them
    We all know here it's not the case, but from someone who isn't aware, that can be
    At least we might try to tag those nice to have or whatnot issues in a way people know its coming and it's not only laying there in wait of nobody knows what
    bigopon
    @bigopon
    that's a nice suggestion. :+1: @EisenbergEffect
    Marc-Andre Roy
    @maroy1986
    Maybe try to have some milestones to tag issues in :)
    If I could do anything to help, just poke me :) I would be glad to help
    Nikolaj Ivancic
    @adriatic
    @maroy1986 @bigopon based on the content od the thread started above ( :point_up: February 28, 2018 8:46 AM), I would think that both of you gentlemen are offering help with Aurelia framerwork open issues cleanup. @bigopon even made a direct "gesture" to @EisenbergEffect , so I would suggest to make such offers in https://github.com/aurelia organization as Rob is more frequent visitor of that organization than https://github.com/aurelia-community.
    Rob Eisenberg
    @EisenbergEffect
    We've got a community member that is recently helping to triage all our issues and help us get some of this under control.
    One of the problems has always been the GitHub permissions model.
    Unfortunately, you can't even label issues without having write permissions for the repo itself, which is a security issue, IMO.
    So, that has caused some issues with actual triage, assigning, etc.
    Marc-Andre Roy
    @maroy1986
    yikes, I see
    Rob Eisenberg
    @EisenbergEffect
    With PRs, I had a regular cadence of reviewing those, but had some work issues for an extended period of time that put me behind on that task.
    I'm in the process of trying to get that back inorder.
    Another issues is the fact that we aren't using a Monorepo.
    When we set Aurelia up originally, there weren't good tools to make that work.
    So, we split everything across a ton of repos.
    That ended up really causing us some problems.
    Marc-Andre Roy
    @maroy1986
    Yeah, agree, would/will be much easier when the switch will be made as you planned it in the roadmap
    Rob Eisenberg
    @EisenbergEffect
    We're working on addressing this.
    We definitely have some issues we need to work through.
    Thanks for the feedback here!
    Marc-Andre Roy
    @maroy1986
    :+1:
    Danny Weldon
    @dannyweldon
    @adriatic Apologies if my comments have oversimplified or misrepresented the documentation process or the portal, which I may have hastily done in my enthusiasm to help. Please feel free to correct any misunderstandings that may have caused. :)
    Nikolaj Ivancic
    @adriatic
    @dannyweldon please do not worry and maintain your level of enthusiasm; that is quite often one of the most important ingredient in OSS projects.
    Nikolaj Ivancic
    @adriatic

    @Didd I found your today's PR , without any comments / answers to my questions posted in our "private" GitHub thread. I would like to discuss with you our next "tack" as the AUCS basic sample collection is very close to be done and we need to create the balance between AUCS Full-stack samples and AUCS Identity Management samples.

    Is there a window in time when we chat in "real time" ?

    Nikolaj Ivancic
    @adriatic

    @all it was fun to think about a project like AUCS, where I tried to play the role of the community organizer, willing to evangelize and do all pedestrian work needed to keep people organized. As it turns out despite many successful activities of this type I did in the past, in this context several things went wrong: I overestimated people's ability to contribute, my own ability to evangelize and underestimated ambitions of a few that wanted to something similar in their own "management".

    I had three pretty good years in the world of Aurelia and I do not regret doing what I did. Time to do something else.

    Didd
    @Didd
    @adriatic ... if you were wondering whether I responded to your query : aurelia-community/AUCS-projects-wide-collaboration#22. I was looking forward to hear back. If you still feel we can get going, I am not faltering.
    Nikolaj Ivancic
    @adriatic
    Hi @Didd
    Yes, we were waiting for each other - state I wanted to avoid, by using the thread aurelia-community/AUCS-projects-wide-collaboration#22. I am sorry for leaving you hanging, feel free to pick this project up, with the caveat that you will likely be the only one doing it :cry:
    Shawn Talbert
    @ShawnTalbert
    @adriatic are you switching away from Aurelia, or just away from managing AUCS? If switchign away, I'd be curious to hear to what you're switching!
    Nikolaj Ivancic
    @adriatic

    My interest in Aurelia is not driven by using Aurelia for developing applications for a fee (as most of the Aurelia Community members do), but rather by desire to help fighting the much richer competitors (Angular and React come to mind) by providing the documentation that is missing. It is missing because despite having a brilliant author with equally good core team all of them are and have to be completely focused on the framework only.

    My great idea was to organize the members of Aurelia community (5000+) who are all great developers (otherwise would not pick Aurelia :smirk: ). As I do not believe that five thousand people would be all so self -centered that I got just 3 people to help AUCS, it ought to be that people like @Alexander-Taran were right saying that I completely failed in organizing the AUCS (note that he is now in the process of creating https://github.com/aurelia-contrib which seemingly has the similar intent).

    In summary: I am leaving Aurelia Community not because of a doubt in Aurelia future, but because of the aurelia community.

    Oh, forgot to say: I am "moving" to AI in general and deep learning in particular.
    Alexander Taran
    @Alexander-Taran

    intent of contrib is to ease in the new aurelia developers experience..
    provide a quick getting started guide and collection of recipes..

    I also want to gather all relevant information scattered all over the blogs/issues and repoes in one place.. like electron-userland does
    That's a dream

    Any willing to contribute members are welcome. Don't see why two initiatives can't coexist.
    We have one repo to dump everything. I believe structure will come.
    Content is the king

    I also triage issues for the main repos
    Sometimes there is a need for small pull requests to core docs.
    I create issues for those in contrib.
    And ppl can just grab those marked 'contribute_to_core'

    Team is very grateful for that. And pull requests get merged in a matter of days.

    Nikolaj Ivancic
    @adriatic
    I agree with all your points and believe that you will be very successful with aurelia-contrib.
    Jean-Michel David
    @jmdavid
    @adriatic @Alexander-Taran Oh! I'm sad to read that AUCS is fading out. It is pretty confusing for a newcomer to get started. On UX project, documentation is thin and the showcase is not updated nor documented often. Now, who can I help and how?
    Nikolaj Ivancic
    @adriatic

    @jmdavid allow me to set the record straight: AUCS and aurelia-contrib are two parallel efforts created to engage members of aurelia community to help augment aurelia technical guides. They are not by any means competitive in their approaches and in theory could be running in parallel if it weren't the case that they are competing for the same resource: amount of good will / available time / perceived value of these two project's outcome.

    • AUCS is pretty well defined here and in order to get going I expected at least 6-7 developers who could afford at least 20 hours a week to spend on this project. At initial count - there were 25 members of the community willing to participate, but when I sent the signal that it is time to start - just one person appeared. There were statements made that I overdesigned the supporting infrastructure (I claim that it is needed for managing the parallel effort of 25 developers), that nobody has the time to read the instructions needed o be able to start spending time on AUCS (perhaps - but I got not a single question how to interpret this or that), so I am guessing that it is the size of AUCS output / expected amount of time that turned people off. Even if this is the correct reason, I have not seen any offer of the type "I would like to work on only this part of the whole - can we do that?

    • aurelia-contrib is a lot more "humble", expecting contributions in a small chunks, without any synchronization needed between the contributor. My only comment to this effort is it's great but it does not address my needs (that I had through 3 years of trying to learn Aurelia).

    That is the summary of AUCS - most people would like to hear a hip-hop song or two - there are also people who would go listen to a long opera. We are all different, so my effort to "present an opera" failed due to lack of audience (as it often happens with real operas)

    Nikolaj Ivancic
    @adriatic

    I need to explain the statement made above

    There were statements made that I overdesigned the supporting infrastructure (I claim that it is needed for managing the parallel effort of 25 developers).

    Unlike aurelia-contrib projects, AUCS is a single (hopefully interesting) story on developing Aurelia applications, which assumes that the used already knows what aurelia-contrib is teaching (tips and tricks, which by the way was one of the part of the AUCS, that seems to be taken over by aurelia-contrib). AUCS is built around a solid state of samples that are used in all different aspects of Aurelia application development (SPA, front end of an client server, Identity Management, application deployment with docker /kubernetes) - technical documentation that would put Aurelia on the same footing with much competitors that have a lot more resources (Angular, React etc.)

    Nikolaj Ivancic
    @adriatic
    To conclude: in the last three years, as a member of the three person team (Aurelia-UI-Toolkits) I contributed to Aurelia three well respected and used plugins (aka bridges) - KendoUI, Materialize and Syncfusion - some of which were direct reason for some large customers to decide to go with Aurelia. That gave me the (false) hope that I could aim even higher by organizing community members to give Aurelia the results of AUCS. In a sense I am happy that I realized how there is no strong enough commitment by the community, at the beginning (discounting my two months worth of work that I spent on it) than somewhere in the middle, when there would not be possible by to exit without some serious shame.
    Didd
    @Didd
    @adriatic I feel how that feels. Your effort is so encouraging and you are so brave. I see that Aurelia wouldn't be here if it weren't for few who believed in it right from the beginning. Kudos to @EisenbergEffect. @adriatic I fully believe in what you intend to do. If not at the super speed you intend the project to get going, can you hope again we can advance it ? Any movement by its nature starts with very few and grows in mobilizing the mass. I feel quite optimistic.
    Didd
    @Didd
    Help wanted :- Code samples here have kicked in. To begin with, guide for 'typescript' have rolled out. Help wanted on writing guides for 'typescript-webpack', 'esnext' and 'esnext-webpack'. The final structure for aulire-cli guide can be found here.
    Nikolaj Ivancic
    @adriatic

    @Didd - There is no sense to try to resurrect AUCS - as it has died without a chance of getting a new life. There are so many other opportunities to do something useful and fresh in a place where you will be properly appreciated. There is a sufficient number of members of aurelia-community organization that have seen your "cry for help" without making a a hint of a response, to recognize that this dog will not hunt

    I believe that AUCS is a noble attempt, presented to the community that did not want to make even a feeble attempt to understand what was being proposed. Whether this is the consequence of lack of respect for me, or my proposal was fully evaluated and assessed as bad - the conclusion that this community does not deserve us, stands :smile:

    See me at https://gitter.im/Didd

    Didd
    @Didd
    @adriatic
    Going through the thread once again since its inception I see the eagerness is there as well as the sense of overwhelm and uncertainty to go about doing something. While your effort has been to do your best to share the clarity and hoping fellows to get going practically. I feel the feelings and taught expressed by everyone is taken to heart while to synch it all up seems a bit baffling. That being the case to get going the hope is to approach it at a natural pace and advance the work and finalize as much guide as we can . The en-devour I feel will naturally attract more and more fellows. "Ah I think I can contribute in this way or I can do that" naturally emerges.
    Prabhsimran Kaur
    @psmrn131
    Did anyone get the following error ever:
    Uncaught Error: No Aurelia APIs are defined for the element: "TABLE". thrown
    bigopon
    @bigopon
    @psmrn131 did you have anything like this in your code?
    <some-element table.ref="..."></some-element>
    btw, you can get answer for your Q much faster by one of the following options:
    Andy
    @weoreference
    @adriatic @Didd I am interested in this project! When can we (re)start?
    Nikolaj Ivancic
    @adriatic
    @Didd - I am going to assume that you are gently pulling my leg, as my now, two years old post (https://gitter.im/aurelia-community/Lobby?at=5aadd226e4ff28713a450138) should explain that AUCS died abruptly two years ago. Luckily, I got an email announcement that you are asking about it now :smile:
    I am not a part of the Aurelia community since my last post above.