I appreciate it. I think just rewording it might fix some issues. An example response I would have liked to hear would have been,
We appreciate the offer you are making to donate or maintain your project at Apache Flex. We know you've worked hard on your project and know your desire is for it to benefit the greater Flex, Flash and web Platform community. Before we can accept your donation we need to make sure of the following things: A. The code being donated is good in legal aspects. C. The code is related to the platform in some way, shape or form. B. The code being donated has some documentation, some examples and if possible the author is accessible to answer questions I understand that in some projects you don't want someone to "dump" a project on you that you won't maintain. But in this sense, in the developer community, a lot of things are a work in progress and under go many revisions. Flex is roughly on it's 8th major revision if you count the original two Flash component sets, Flex 1-4 and one or two major revisions of FlexJS / Falcon, not counting Starling, Feathers and other related revisions. So the components Tink donated years ago IIRC weren't completely finished (from what I read at the time they were still in progress) or that he may not even be part of the community anymore to maintain it. I still would have liked to have his and others work integrated into a sub swc whether they completely fit or not. Plus it's important to remember that people move on, change jobs, change careers whatever. Alex wrote: > So to be more clear, I am interested in collecting things related to Flex that the community wants to maintain and improve. AS3Commons, SWIZ, Parsley, and all of those other 3rd party things that lots of folks use and are afraid the server that serves them might go away. But only if we have folks here willing to help maintain and create releases for that code, which is why there will be votes on each one. I agree. I can't tell you how many sites are down that used to host Flash and Flex code (all because of bad marketing Flash muckraking). But even if the projects are dead the least we could do is provide a graveyard here so if we ever need to dig up their rotting corpses we can do so ...ok bad analogy (I read too much hellboy). @Mark & @Chris & @Justin When I said vetting, I meant going through the legal process. I agree on that part. I agree we need to make sure it's something we can all use without worrying about copyright issues. On Mon, Apr 18, 2016 at 12:01 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote: > Jude, > > First off, I am truly sorry that you had a bad experience at Apache Flex, > especially when you were trying to do good to the community by donating > something that you had put your heart and soul into. > > We are all learning here. Instead of saying let's not do this at all, > perhaps you can propose a better way of doing things. Where we don't look > like dicks, at the same time we make sure that > A. The code being donated is good in legal aspects. > B. The code being donated is something that the community needs/wants > C. The code being donated is not just getting dumped because no one else > wants to deal with it. > > You are in the system now. Be the change you want to see in the world. > > Thanks, > Om > On Apr 18, 2016 4:35 AM, "jude" <flexcapaci...@gmail.com> wrote: > > > Slightly off topic, but if someone is kind enough to give you a gift, the > > proper response is to say thank you and accept it. What you do after you > > accept it is another story. > > > > The Apache process of discussing if we should accept said gift is kind > of a > > dick move. No offence, but IMHO this behaviour has to stop. And this is > not > > directed at you Harbs or anyone in particular. > > > > I'm not saying we don't need to vet a donation, or decide if it should go > > into core or be setup as a side project. But if someone wants to donate > > code they own or built and it's legal then accept it and move on. > > > > People, and myself thought that Apache Flex was going to be the place > where > > we make Flash and Flex thrive again. I thought we'd have plenty of > donated > > components and projects but you hear someone offer to donate something > and > > then it seems to die and you don't hear from them again. > > > > It's a huge turn off to work on a project, want to donate it and then > hear > > your community start talking about if they should accept your donation > or > > not. That's not progress is suppression. > > > > IIRC Alex once said he's interested in collecting everything related to > > Flex (and the Flash Platform?) here. So am I. And that's good enough for > > me. > > > > From my perspective, Apache has some anti social processes and procedures > > in practice. But the guidelines say quite clearly that a community can > run > > itself how it seems fit. So, something needs to change in my opinion. > > Sorry, if I'm ranting. > > > > Anyway, I want to include lihzi's code and keep the package name the same > > for the reasons Harbs mentioned and if any future projects are cross > > compiled we avoid problems by that as well. > > > > I also suggest we adopt a process to accept license compatible platform > > related future donations automatically and let our discussions focus on > > whether they should be in core or in a secondary location. > > On Apr 17, 2016 6:06 AM, "Harbs" <harbs.li...@gmail.com> wrote: > > > > > Lizhi has put together some impressive classes to implement the Flash > > > drawing APIs for FlexJS using Canvas.[1] > > > > > > Lizhi has offered to donate the code[2] and I believe has just filed an > > > ICLA. > > > > > > The question now remains whether we want to include the code. I > > personally > > > see a lot of value in the code as it offers a lot of functionality > users > > > are used to out of the box using the same APIs. > > > > > > I do have some questions about accepting the code: > > > 1. Whether to keep the packages as they are. Currently, they use the > > > flash.* packages to match the ones in playerglobal. One the one hand, > > this > > > makes a lot of sense in terms of migrating code because everything > stays > > > exactly the same. On the other hand, the package names are misleading > as > > > it’s not “Flash” packages. The alternate would be to wrap things in > > apache > > > flex packages, but that would add a lot of work in terms of conditional > > > compilation and redirection. I also don’t know if there are legal > issues > > > with using the “flash” package. I can’t imagine what they might be, but > > > INOL… > > > > > > 2. How should these files be organized in FlexJS? This might be related > > to > > > the package names, but might not. I assume this is not “core”. Should > it > > > all go into a single project, or should it be split up into multiple > > > projects? > > > > > > Harbs > > > > > > [1]https://github.com/matrix3d/spriteflexjs > > > [2] > http://mail-archives.apache.org/mod_mbox/flex-dev/201604.mbox/browser > > >
