Re: [Coapp-developers] Another Topic - IRC channel?

I'm really glad there's someone left who uses IRC ;) Regarding logging bots, this normally involves a script which stays joined to the channel, running on a server somewhere and saving all the lines in the channel to a database/text file. On Fri, Apr 9, 2010 at 11:55 AM, Elizabeth M Smith < ems

Re: [Coapp-developers] Another Topic - IRC channel?

Furthermore, what I have seen other projects do is call an IRC meeting, which is then logged manually. That way project related discussions can be more easily used as the basis for spec-writing, blueprints etc. On Fri, Apr 9, 2010 at 4:32 PM, Adam Baxter wrote: > I'm really glad there&#

[Coapp-developers] Preliminary ideas

I'm slowly getting some ideas down at: http://wiki.github.com/voltagex/projects/coapp (sorry for external link, I needed some formatting) I split my ideas into * Update system How application updates would work * For Programmers How programmers would make use of CoApp * Policies "Rules"? * Tec

Re: [Coapp-developers] How exactly will CoApp come together?

As the package spec will be available to all, there's no reason there couldn't be multiple tools to do the same job. I'm already thinking about a tool to package Python programs for MSI/CoApp. On Tue, Apr 13, 2010 at 2:48 PM, Andrew Fenn wrote: > Is there a reason to collect all the data using t

Re: [Coapp-developers] Let's talk about libraries

>In order to use WinSXS however, all binaries must be signed with an Authenticode code-signing certificate, from a reputable CA (certifying authority). This is automatically a major roadblock for many open source projects. On Tue, Apr 13, 2010 at 3:49 AM, Garrett Serack wrote: > Since I’ve been

Re: [Coapp-developers] CoApp conference call and Presentation

Bouncing this back to the list -- You'll have to get all our timezones first :) I'm in UTC+10. On Fri, Apr 16, 2010 at 9:31 AM, Garrett Serack wrote: >I’d like to set up a time we can have a presentation and conference > call so people have an opportunity to ask some questions, and perha

Re: [Coapp-developers] Visual Studio Dependencies

I'd just like to remind everyone that Visual Studio Express users don't get plugins. On Thu, Apr 15, 2010 at 10:57 AM, Garrett Serack wrote: > Hmm. > > [Longer Term] a package browser in Visual Studio that gets a list of > library packages from the repositories. > > G > >

Re: [Coapp-developers] What packages do you want to see?

1 GTK (perhaps on the developer side of things - this is normally tricky to bundle with applications) 2 OpenSSL/SSH Server 3 Notepad++ (thinking of CoApp more as a package manager) 4 PortableApps ___ Mailing list: https://launchpad.net/~coapp-developers P

Re: [Coapp-developers] What packages do you want to see?

Thinking about this another way: >From my Debian box, I want to be able to *apt-get coapp-build co-buildpkg mycoolapplication *So far, only the NSIS installer can build a Windows installer from a Linux-based host. On Thu, May 6, 2010 at 6:35 AM, Garrett Serack wrote: > True, True. True. True. >

Re: [Coapp-developers] What packages do you want to see?

The compromise may be a *nix utility to verify that everything's ready to send to CoApp. If there are some developers who can't afford a copy of Windows, that's probably one instance where CoApp as an organisation would be really helpful. ___ Mailing list

Re: [Coapp-developers] What packages do you want to see?

> > What about allowing a project maintainer to root the sandbox to their > application > when subscribing to the build results? That way they could have > confluence-like > builds of their app in almost real time, which is as useful as installing > the > CoApp toolchain and running it on their ow

[Coapp-developers] CoApp from different perspectives

The Open Source developer * CoApp provides a way to gain a wider audience for my application * CoApp provides a way for my application to be "production-ready" on Windows The freeware developer (think PortableApps) * An alternative to "download-catalogue" sites which often require a large amount o

Re: [Coapp-developers] CoApp from different perspectives

Maybe we could ask the Word 2010 team if we could borrow their "Send a Smile" and "Send a Frown" apps - that's the neatest way I've seen to report bugs, albeit a little simplistic. ___ Mailing list: https://launchpad.net/~coapp-developers Post to : co

Re: [Coapp-developers] What packages do you want to see?

>I assume by "users" you mean "developers" Not necessarily. The QT libraries are 6MB (QT Core and QT GUI), and the Windows apps I've seen so far are dynamically linked. If CoApp packages mean users only have to download the QT libraries once, that'd be quite helpful for people on low-bandwidth and

Re: [Coapp-developers] Is it a project goal to in the end have a CPAN/GEM/CheeseShop for .NET components?

Just noticed this thread. .NET packages will have their own package category (I think?), so eventually you'll be able to filter on .NET libraries or whatever you're looking for. Might be worth looking at the popularity lists on CodePlex/CodeProject and others to see what the most used .NET apps an

Re: [Coapp-developers] What packages do you want to see?

* wget (currently has no Windows maintainer), has a great Windows port though curl, just because it's curl *** pcap - would be a good test case for our driver packages ** libusb - same reason as pcap, also missing a windows maintainer * grep - who doesn't love grep? ___

[Coapp-developers] WGet as a case study

Most, if not all of you should know of wget. Unfortunately wget doesn't have a Windows maintainer at the moment. http://www.mail-archive.com/bug-w...@gnu.org/msg00796.html The "latest" build I can find of it is http://www.christopherlewis.com/WGet/WGetFiles.htm A VS2005 solution at http://www.chris

Re: [Coapp-developers] WGet as a case study

Maybe case study was the wrong phrase. Easy target possibly. In any case, wget has the normal interesting dependencies, such as openssl. On Tue, May 18, 2010 at 4:50 PM, Ted Bullock wrote: > On Tue, May 18, 2010 at 12:15 AM, Adam Baxter > wrote: > > Most, if not all of you should

Re: [Coapp-developers] WGet as a case study

>How about something cool like Blender for a case study. Would Yo, Frankie! be acceptable? ;) www.yofrankie.org On Tue, May 18, 2010 at 4:50 PM, Ted Bullock wrote: > On Tue, May 18, 2010 at 12:15 AM, Adam Baxter > wrote: > > Most, if not all of you should know of wget > &

Re: [Coapp-developers] Code?

50k multiplied by how many downloads/packages? ;) On Wed, May 19, 2010 at 3:19 AM, Olaf van der Spek wrote: > On Tue, May 18, 2010 at 4:50 PM, Garrett Serack > wrote: > > Yes, we'd like to have a tiny bootstrap DLL that gets us the engine DLL, > and the bootstrap can ship in every MSI. > > > > T

Re: [Coapp-developers] Choice of License.

Agreed. AL 2.0. On Wed, May 19, 2010 at 3:33 AM, Nasser Dassi wrote: > I concur with Garrett's recommendation of AL 2.0. > > The language translates to the same thing with 3 specific exceptions: > > * AL 2.0 is explicitly *no-charge*. > * AL 2.0 is explicitly *irrevocable *(as bold-faced). > * A

Re: [Coapp-developers] What packages do you want to see?

so - both have windows ports that are a bit out of date. I think they would be good targets to coapp-ify -- Sent from my Nokia N900 - Original message - > On 5/18/2010 12:05 PM, Jernej Simončič wrote: > > On Tuesday, May 18, 2010, 17:28:48, Henry Rodrick wrote: > > > > > Awesome tip, than

Re: [Coapp-developers] Creating Projects in Launchpad.

How does Ubuntu do all of their packages? I don't think they need to all have the co- prefix because by being linked to the CoApp project we know the context of them. On Wed, May 19, 2010 at 3:08 AM, Garrett Serack wrote: > FYI: > > > > I’ve requested the CoApp project be renamed to CoApp-Engin

Re: [Coapp-developers] Choice of License.

Thanks Nasser, Are we done here? I'd like to get back to some code now. On Wed, May 19, 2010 at 2:10 PM, Nasser Dassi wrote: > Just to bring everyone's attention back to topic, here are the licenses in > question: > > Alphabetical listing of OSI Licenses -- > http://www.opensource.org/licenses/a

Re: [Coapp-developers] Creating Projects in Launchpad.

ubuntu packages are under an ubuntu/ namespace, so I'm assuming we can get a coapp namespace. On Wed, May 19, 2010 at 7:14 PM, Olaf van der Spek wrote: > On Wed, May 19, 2010 at 12:43 AM, Adam Baxter wrote: > >> How does Ubuntu do all of their packages? >> >> I don&

[Coapp-developers] [specs] Pre and post install actions?

Hi, Do you think each package type should have pre and post install actions? For example, * an executable package might register itself to the Games Explorer on Vista/7 after installation * a source package might need a very specific folder structure * an executable might require non-CoApp resourc

Re: [Coapp-developers] [specs] Pre and post install actions?

upports. > > > > Custom Actions are one of the worst parts and most abused features in MSI. > > > > > > > > *From:* coapp-developers-bounces+garretts=microsoft.com@ > lists.launchpad.net > [mailto:coapp-developers-bounces+garretts > =microsoft@lists.l

Re: [Coapp-developers] [specs] Pre and post install actions?

her. > > Activation keys are needed to run something, not install it, so the > app should really ask itself at first startup. > > Registry additions have WiX elements, it's not an action either. > > Adam K > > On 19 May 2010 22:29, Adam Baxter wrote: > > Hi, &

[Coapp-developers] [wiki] Glossary

I've started a glossary section on http://coapp.org/Blueprints/Definitions. Feel free to add/delete/move as necessary. Some of the definitions may require links to MSDN or their own separate wiki page. If the glossary gets too big for that page, we can move it off into its own page under Blueprint

[Coapp-developers] [package] GStreamer

I know it's early days yet, but I thought the GStreamer audio/video framework was worthy of attention, both because it's quite popular, and because it's really hard to build on Windows. http://gstreamer.org/features/index.html https://launchpad.net/hsbuild is GStreamer's Windows build system, and

[Coapp-developers] [package] wget

Sorry for list spam, just testing a method of tagging discussions. 2010/5/19 Roberto Carlos González Flores > I gues that i'm a command line guy too, because i think we need to study > wget. > > 2010/5/18 Mark Stone > > On Mon, May 17, 2010 at 11:50 PM, Ted Bullock >> wrote> >> > >> > Hmm, jus

Re: [Coapp-developers] Trying to prioritize things

Launchpad site/s set up Sample MSIs + source On Fri, May 21, 2010 at 2:25 AM, Garrett Serack wrote: > Hey folks, > > > > I’m trying to prioritize all the crap on my plate, and I don’t want to drop > anything so I need everyone who is blocking on something from me, to reply > to this mail with ONE

Re: [Coapp-developers] Anyone with OData experience out there?

And, if you require a web service for everything to work, you make the task of mirroring a CoApp repository that much more difficult. On Fri, May 21, 2010 at 1:00 AM, Olaf van der Spek wrote: > On Thu, May 20, 2010 at 4:49 PM, Trent Nelson wrote: > > Now, this is the point that my 15 minutes of

Re: [Coapp-developers] Anyone with OData experience out there?

Please please please do not impose too many requirements on future mirror hosts. Fedora/YUM uses a plain XML file to host repository data. At least allow a non-webservice fallback. http://mirror.centos.org/centos/4/csgfs/x86_64/repodata/repomd.xml http://mirror.centos.org/centos/4/csgfs/x86_64/re

[Coapp-developers] [wishlist] [future] Non-webservice fallback for repository XML + mirror requirements

Before running away with OData too much, consider the implications of requiring each mirror host to run web services. For the mirror hosts: Most Linux-based packaging systems allow mirroring of the *entire *package tree, and it's no more complex than running (r)sync between mirrors. For the user

Re: [Coapp-developers] [wishlist] [future] Non-webservice fallback for repository XML + mirror requirements

ing open-source to Windows... > and not necessarily keeping everything in the Linux portion of the world. > > - nasser > > On Thu, May 20, 2010 at 9:58 PM, Adam Baxter wrote: > >> Before running away with OData too much, consider the implications of >> requiring each mirro

Re: [Coapp-developers] TakeoffGW

Closer to the mark is https://launchpad.net/hsbuild ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.ne

Re: [Coapp-developers] Whiteboard Pictures from the summit

http://www.flickr.com/photos/voltagex/tags/coapp/ ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/L

Re: [Coapp-developers] Building CoApp code!

The Windows SDK link you provided is the Win 7/.NET 3.5 version. Will we also need the .NET 4 version? On Tue, Jun 8, 2010 at 1:48 PM, Garrett Serack wrote: > 1. Install (to the default path!): > > - Visual Studio 2010 > > - Windows DDK (http://bit.ly/95Bl28) > > -

Re: [Coapp-developers] Async notification from CoApp Engine (libCoApp)

2010/6/10 Jernej Simončič : > of course, I've yet to see list management software that exposes > this setting to the individual subscriber - not like it's more > important than 20 other settings most mailing lists expose) https://launchpad.net/~launchpad-dev ;) I'm sure we could submit a fix somew

Re: [Coapp-developers] Building CoApp code!

Feel free to post it up - if you've signed up to Launchpad you have your own personal Bazaar repository. https://code.launchpad.net/~[username]/+addbranch ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.laun

Re: [Coapp-developers] Plugins in vs2010

Are these distinct from addons? --Adam ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp

Re: [Coapp-developers] IA 64

Nope. ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp

Re: [Coapp-developers] The CoApp site needs some love

Looks like it'll turn into a team effort. I'll join in if anyone needs a hand (ASP.NET/PHP) On Sat, Nov 13, 2010 at 12:54 AM, Nasser Dassi wrote: > Sounds like something I do for a living (esp. the being-a-master part). > > I'll try to hop into the IRC chan today to discuss further... > > - nass

Re: [Coapp-developers] The Syracuse Experiment.

Sorry Garett, that was meant to go to the list. -- It's all interesting, nonetheless. Also, the documentation produced is of quite a high standard! This may be useful for us later, and some of the design work could definitlely be used. --Adam ___ Mail

Re: [Coapp-developers] Ninite

Ninite is a great way to focus on users. CoApp will also focus on developers - and we are aiming to have a bit more customizability than Ninite does. --Adam On Sun, Apr 10, 2011 at 4:31 AM, Mark Stone wrote: > This looks like something we ought to be paying attention to, and have > an opinion on.

Re: [Coapp-developers] Ninite

It'd be great to have a one-click interface as an option for CoApp though. On Wed, Apr 13, 2011 at 12:43 AM, Garrett Serack wrote: > Ninite just puts together a collection of known-working-installers.  They > pretty much expose the "product discovery" scenario, and streamline the > installation

Re: [Coapp-developers] Moving to github today

Cool, also other DVCSes have good integration to Git. If you want to work in Mercurial, or keep your own copy in Bitbucket or similar, you can use http://hg-git.github.com/ If you want to work in SVN, GitHub supports that natively. CVS probably works too, but you're crazy. For VS2010, please u

Re: [Coapp-developers] Blogged: "Shallow-forking a project" for #CoApp

So the libjpeg example in your post already had .vcxproj files for it? What extra steps would be required for a project that's never had a Windows/Visual C++ build? Let's assume for the moment that it'd be simple enough not to require any Windows-specific code changes, and that we're only talking

[Coapp-developers] Shallow-forking win-iconv

I've had a basic attempt at converting win-iconv (in preparation for wget) to build in VS2010. It will build if you right click the relevant source file and hit compile, but not as a solution because the test file redeclares methods that the main file uses. I'm not sure how build order and build de

Re: [Coapp-developers] Shallow-forking win-iconv

OK, so the project I currently have in there, what's it actually meant to build? Do I need any code in the second project or do I just add a reference to the main project and set the output to .dll? On Sun, May 15, 2011 at 12:02 PM, Jonathan Wilson wrote: > Adam Baxter wrote: > >

Re: [Coapp-developers] Shallow-forking contest!

winners get their MSDN subs renewed? ;) On Jun 3, 2011 1:15 AM, "Garrett Serack" wrote: > Hey folks, > > (not an official announcement yet!) > > We're reaching a stage in the CoApp project where we can really use the help of Windows developers to assist us in shallow forking open source projects a

Re: [Coapp-developers] Did ya guys see this?

So for someone like me, who's having lots of trouble building packages from source with the VC++ compiler, will this eventually make it easier for me to get working .vcproj files? --Adam On Fri, Jun 10, 2011 at 1:29 AM, Garrett Serack wrote: > http://fearthecowboy.com/stuff/Distilled.tmp.html**

Re: [Coapp-developers] Using coapp

On Sun, Jun 26, 2011 at 2:13 AM, Orhun Birsoy wrote: > Hi, > I using 15+ open source projects for an application I am working on. I > maintain home grown python scripts to build most of the projects but others > are still manual process. In the pursuit of fully automating the process I > decided t

Re: [Coapp-developers] LaunchPad

Off the top of my head, and others *please* correct me * Mailing list delivery reliability - sometimes we were unsure if everyone was getting messages * General launchpad.net slowness * Bazaar feels a lot less flexible than alternatives * Less integration on launchpad.net with source control than s

Re: [Coapp-developers] Added features to command line coapp applications

I wonder if this should be optional metadata for 3rd party packages, too - i.e. BugTracker for [MyGreatApp.msi]: http://example.com/bugs On Wed, Jul 13, 2011 at 4:42 AM, Garrett Serack wrote: > I’ve added a feature to the command line parsing stuff that makes it > simpler to get to the bug track

Re: [Coapp-developers] Could someone do a comparison chart between RPM & Apt-get command lines

Please implement tab completion! On Wed, Jul 20, 2011 at 1:33 AM, Garrett Serack wrote: > I want to make sure that the CoApp cli is as comfortable as possible to > folks used to Linux package management tools. > Honestly, I haven't stopped to look at the command lines for RPM and > Apt-get, and i

Re: [Coapp-developers] Changes to the design of CoApp

I agree, given that we're already going to be elevating via UAC. ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help

Re: [Coapp-developers] CoApp Service Messaging API published (draft)

Could we get a Version command as well? I'm thinking far in the future about remote management and the like. On Wed, Aug 10, 2011 at 6:18 AM, Garrett Serack wrote: > https://github.com/coapp/coapp.org/wiki/Coapp-service-engine---interface* > *** > > https://github.com/coapp/coapp.org/wiki/Servic

Re: [Coapp-developers] CoApp Service Messaging API published (draft)

Definitely, so if I have a web or WSUS frontend, I can identify the versions of the CoApp backends I'm dealing with. ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchp

Re: [Coapp-developers] Weekly CoApp Technical Discussion Conference Call: Fridays 10:30AM PDT

Yes! 4.30am! On Fri, Aug 19, 2011 at 9:14 AM, Garrett Serack wrote: > When: Friday, August 19, 2011 11:30 AM-12:30 PM. (UTC-08:00) Pacific Time (US > & Canada) > Where: Online Meeting > > *~*~*~*~*~*~*~*~*~* > > Gotta push this week's meeting out an hour to 11:30 PDT. > > G > > > The last couple

Re: [Coapp-developers] CoApp and

I'd just stick with a LICENCE file in the package, and use a parser like Debian's build system does (matches common licences) This just sounds like complication for complication's sake. Interesting idea though. --Adam ___ Mailing list: https://launchp

Re: [Coapp-developers] Shallow Fork Sprint Weekend

Looks like some of the formatting didn't work IRC channel is at irc://irc.freenode.net/#coapp or http://webchat.freenode.net?channels=coapp if you don't have an IRC client installed. ___ Mailing list: https://launchpad.net/~coapp-developers Post to :

Re: [Coapp-developers] Shallow Fork Sprint Weekend

An initial attempt at making winiconv build under VS2010 is at https://github.com/voltagex/coapp-winiconv - sorry about the state of the repo, hg-git conversions don't seem to work too well. ___ Mailing list: https://launchpad.net/~coapp-developers Post t

Re: [Coapp-developers] Idea for package comments/feedback/ratings

> The only thing we’d have to do is put in a browser control into the UI (and > we can obviously lock what it can do down), and present the appropriate view > to the user. > > ** ** > > We could either use the IE WPF widget, or it turns out there is another > based on the Chromium/Webkit engine

Re: [Coapp-developers] I think we'll want to fork gnulib

Sounds interesting from a porting point of view, but are we setting ourselves up for a situation a-la Cygwin where we've got a modified "layer" sitting underneath our apps? --Adam ___ Mailing list: https://launchpad.net/~coapp-developers Post to : c

Re: [Coapp-developers] I think we'll want to fork gnulib

> > I think that depends on how far we're willing to go to avoid modifications > to the original source. If we tried to provide grep with the failure code it expects, I think that would bring us into compatibility layer territory. Instead, we should just accept that that's how windows works and

Re: [Coapp-developers] I think we'll want to fork gnulib

Err, not sure how I mashed my signature there... On Mon, Sep 26, 2011 at 10:35 PM, Adam Baxter wrote: > I think that depends on how far we're willing to go to avoid modifications >> to the original source. > > If we tried to provide grep with the failure code it expects, I

Re: [Coapp-developers] I think we'll want to fork gnulib

Do you end up with an #ifdef soup with this approach? The two things that spring to mind here: * Library A needs work to make it good for us. Library A is then updated - what work do we need to do keep pace with mainline? * Do we try to get Windows specific patches integrated back upstream at any

Re: [Coapp-developers] Blogpost: A new approach to strong naming and signing of Windows and .NET binaries

That is very, very cool - and may actually be useful in my day job. Thanks Garrett! --Adam ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers

Re: [Coapp-developers] Awesome documentation for CoApp

So into the wiki idea, add approved revisions - that way you get the benefits of wikis with some versioning and publishing. On Dec 17, 2011 9:52 AM, "Mateusz Łoskot" wrote: > 2011/12/16 Garrett Serack : > > Well, since I'm going to spend the next week or so writing docs, I'll > start by chiming i

Re: [Coapp-developers] Website documentation progress

Just a note - fairly sure that Notepad++ uses the Scintilla components from SciTE anyway! 2011/12/21 Garrett Serack > Really, it has nothing to do with "Windows" as much as just the way > notepad is written. > > There's not really much in Windows that cares about LF vs CRLF, it's > just what t

Re: [Coapp-developers] Website documentation progress

Nice. This is probably the time I should bring up moving and updating some blog entries. http://fearthecowboy.com/tag/coapp/ They seem to show up fairly high in Google/Bing searches. 2011/12/24 Mateusz Łoskot > On 21 December 2011 01:46, Garrett Serack wrote: > > As you can see, I've started

Re: [Coapp-developers] Should we have a conference call tomorrow?

Just had the same thought. Happy New Year ('s Eve) to everyone...doubtful I'll make a conference call as I've just looked at the clock and it says I should have gone to sleep some time ago. ___ Mailing list: https://launchpad.net/~coapp-developers Post t

[Coapp-developers] Coapp.org dead?

With hours to go until the new year, coapp.org appears to be down :P (placeholder page) ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers Mor

[Coapp-developers] Conference call tomorrow?

See title. ___ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp

Re: [Coapp-developers] Conference call tomorrow?

I really don't like timezones. 2012/1/6 Jernej Simončič : > On Friday, January 6, 2012, 9:06:21, Adam Baxter wrote: > >> See title. > > Not today? > > -- > < Jernej Simončič ><><><><>< http://eternallybored.org/

Re: [Coapp-developers] Anyone on the list going to FOSDEM this weekend?

Any idea if your talk will be streamed? http://fosdem.org/2012/news/video-streaming-urls On 2 February 2012 12:33, Garrett Serack wrote: > Awesome; I’ll make sure I drop by. > > > > Spread the word about my session J > > > > G > > > > From: Pau Garcia i Quiles [mailto:pgqui...@elpauer.org] > Sen

Re: [Coapp-developers] Important CoApp Conference Call tomorrow -- ONE HOUR EARLIER!

4.30am. Whimper. On 17 February 2012 12:49, Garrett Serack wrote: > There will be a CoApp Conference call on Friday, however,* I'm going to > move it up an hour, since I have a hard stop at 11:00am.* > > So the conference call will be at *9:30 am > PST

Re: [Coapp-developers] Northwest Open Source Hackathon Announced

Would love to attend but the commute is a difficult one :P --Adam On 20 April 2013 04:55, Garrett Serack wrote: > Northwest Open Source Hackathon > > What is it: > > An opportunity for Open Source Developers to come together, and get some > things done. We’re bringing folks together from differe

Re: [Coapp-developers] dynamic loading

On 4 June 2013 01:02, Garrett Serack wrote: > I have no problem with that. > > Really, if we want to support an option, that ends up being a custom pivot > for that library... and obviously multiplies the package size out > considerably. > > I'm probably misunderstanding how this works, but why c