On Fri, Jun 24, 2011 at 1:54 AM, Alessandro Volz <[email protected]>wrote:
> Let me put it another way. I will not allow LGPL code in Growl, nor GPL >> code. >> > > Ok, I'll have to rewrite that code. > > >> I worked on reading the Mail.app defaults, it's almost ready. Indeed, the >>> MailMe configuration is much easier, but it doesn't always work. >>> >> >> Oh ya, agreed. That's why it's nice to see this work that you have done. >> > > The only thing I'm asking myself is, will the plugin (the growl helper) be > allowed to access keychain items that belong to Mail.app? Will the user be > asked to allow us to read, or will the OS just block us? I'll see. > > >> We have some paperwork stuff we need to do to get Growl into the MAS as >> well, so I'm really expecting more along the August time frame. That said, >> we're not going to hold Growl to get this plugin in. >> > > I won't be asking you to ;) > I think that if we end up needing a 1.4 for the rollup if that's not done for 1.3, then this could fit in there nicely (of course, depending on when you get done and it's reviewed and what happens in 1.3 and beyond). > > >> Really, I also think the inclusion in Growl is the way to go for this >>> plugin to have any success. I built the plugin because I needed it anyway, >>> but now that it's there, the more people use it the better. The only thing i >>> ask is that my name stays on the prefs pane - I'm not asking you to put me >>> in the Growl devs list. >>> >> >> We'd gladly have you as a dev though. I think it'd be good to have someone >> who can work on plugins and things of that nature. >> > > I could also work on the main project later. Let's not talk about this > until you'll have reviewed the plugin's code, once it's finished. > > Indeed. The Growl Project pretty much lets anyone become a developer who expresses interest. It's a large part of why we had a lot of people join the project a number of years back. Feel free to look us up on irc for a more direct conversation if you're interested. > 1) Licensing: I'll ask my colleagues and let you know. >>> >> >> Oh is there more than just you? >> > > The OsiriX project is more than just me, but the classes I recycled are > 100% written by me.. But I wrote them for OsiriX, and I'm paid for that. > > What I asked my colleagues is, what are the requirements if another project > wants to reuse parts of OsiriX? The answer is, just include something like > "This plugin/app uses some classes from the OsiriX project, which are LGPL." > > Anyway, I'll do the effort of using just NSStreams, and the question is > solved. It'll just take more time. > > I really appreciate it that you're willing to change this up. It means a lot to me. Chris > Alessandro > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
