Re: [Wintermute-devel] Rolling Release Vs. Versioned.

2011-08-31 Thread Jacky Alcine
Test suites, yes. Those only work out well when we have reported bugs or are testing out the abilities of a feature set. As for rolling releases, we're a while away from that. Those work well when the system's working in an expected manner (like the NLUI working okay-ish). We could hit rolling rel

[Wintermute-devel] [info] Qt Provides Cryptography

2011-08-31 Thread Jacky Alcine
I was going through the repository in search of an existing library that provide encryption and decryption of GPG or OpenPGP messages. Then I fell upon QCA. It's modeled after the Java Cryptography Architecture, but the Qt Cryptography Architecture (available by running "sudo apt-get install li

[Wintermute-devel] [info] Packaging Information

2011-08-31 Thread Jacky Alcine
Just so we can keep a consistency in our packages, whether they be Debian packages or RPMs, the content below would be an example "control" file. < data, jargon > Description: Wintermute - an intelligent agent (data library, development files) ##Wintermute is an modular intelligent

[Wintermute-devel] [info] Versioning Scheme

2011-08-31 Thread Jacky Alcine
Best I get this out of the way first. There's a bit of a versioning scheme up on the Synthetic Intellect Institute's Wiki, but I guess it's best to address to all developers so we'd know. Wintermute uses a three-component version scheme, appending occasionally version flags such as (alpha, be

[Wintermute-devel] [info] Development Positions

2011-08-31 Thread Jacky Alcine
Since the majority of this team spans across the globe and I've been temporarily decommissioned; I see it unfair to the project to have to wait for each time I find a laptop or PC that has access to the Internet to push code every two weeks. Thus, the following roles are proposals that could be

[Wintermute-devel] [info] (part 1 of 3) Wintermute Awareness

2011-08-31 Thread Jacky Alcine
Now, this is something that I know will excite a few. Wintermute's ability to really mine for data, or in this sense, generate ontological information from raw data from its environment and use said data to enhance its own abilities. Right now, Wintermute isn't able to remotely aware of anything

[Wintermute-devel] [info] (part 2 of 3) Wintermute's Data Mining

2011-08-31 Thread Jacky Alcine
Data mining is perhaps Wintermute's biggest tool. Without its ability to obtain information about its environment, Wintermute only knows what it does within the COSMO ontology. And that, compared to the vast amounts of information out there in the world, is NOTHING. Another beautiful aspect of

[Wintermute-devel] [info] (part 3 of 3) Wintermute's Metadata

2011-08-31 Thread Jacky Alcine
Metadata is perhaps Wintermute's ontological "bread and butter", so to say. Metadata, in the orb of Winty, would be merely a definition of a base class in the ontology about things Wintermute can bluntly speak about. We would also need to provide an unknown class type (UnrecognizedMetaData) to

Re: [Wintermute-devel] Rolling Release Vs. Versioned.

2011-08-31 Thread Adrian Borucki
In future we perhaps design some test suits so in case of small changes they often should be easily testable. Now we must focus on rigorous specifications to get good notion of Wintermute's structure. This will take some time but I think it is worth doing. On 31 August 2011 22:13, danteash...@gmai

Re: [Wintermute-devel] Rolling Release Vs. Versioned.

2011-08-31 Thread danteash...@gmail.com
After testing, yes. Me thinks we should focus on stabilty and polish, rather then new features. On 31 August 2011 21:06, Adrian Borucki wrote: > On 31 August 2011 21:24, danteash...@gmail.com wrote: > >> How exactly do you mean, Adrian? That the packages be .deb (as opposed to >> .rpm)? > > I m

Re: [Wintermute-devel] Rolling Release Vs. Versioned.

2011-08-31 Thread Adrian Borucki
On 31 August 2011 21:24, danteash...@gmail.com wrote: > How exactly do you mean, Adrian? That the packages be .deb (as opposed to > .rpm)? I mean that when new version of software arises we release new package and it is immediately installed as an upgrade. > > I do think we should retain versio

Re: [Wintermute-devel] Rolling Release Vs. Versioned.

2011-08-31 Thread danteash...@gmail.com
How exactly do you mean, Adrian? That the packages be .deb (as opposed to .rpm)? I do think we should retain versioning; Lets say we have 1.0.0 released 1.0.1 would lead up to the next minor 'landmark' (when released, all ISO's etc would default to that) and 1.1.0 is more of a landmark, rather th

Re: [Wintermute-devel] Rolling Release Vs. Versioned.

2011-08-31 Thread Adrian Borucki
On 31 August 2011 18:29, SII wrote: > Hello all. > > I've been thinking; if everything goes to plan, WIntermute should be able > to automatically upgrade itself to the latest version. > So, with that in mind, when the system is finally ready to be released; why > don't we go with a rolling releas

[Wintermute-devel] Rolling Release Vs. Versioned.

2011-08-31 Thread SII
Hello all. I've been thinking; if everything goes to plan, WIntermute should be able to automatically upgrade itself to the latest version. So, with that in mind, when the system is finally ready to be released; why don't we go with a rolling release model, instead of a versioned one?