[Developers] Metaweb Framework (renamed)

[Hayden Stainsby]

I think I'm siding more with Jason with regards to having at least  
some properties for specific URLs (probably code repository,  
documentation and similar), but I think this would probably be best  
served by a separate type. As the same properties could be used for  
many other software projects.

Having said that, not all software has code repositories, wiki pages  
etc. So perhaps a type, 'collaborative software' could be used, this  
could then apply be applied to metaweb software/frameworks as well as  
other software - one of the main differences being that a something  
of type metaweb software will have more centralised information on  
freebase - and will most likely be developed by a freebase user (or  
users).

Of course any thoughts, suggestions etc. is most welcome.

On another subject, was it intentional that someone posted to Free  
Developers <developers at freebase.com> or was it a cute mistake. I  
check my backlog and it happened before I ever posted to the list. (-:

--
Hayden

On 14 Aug 2007, at 18:35, Jason Douglas wrote:

> We'd like to add a "Frameworks" type to the developer section of  
> the site for listing these kinds of projects.  Adding a property  
> for things like wiki pages, code repositories, etc. would make  
> sense to me.
>
> Hayden started working on a type like this in his own account here:
> http://www.freebase.com/view/filter?id=%2Fuser%2Fhds% 
> 2Fdefault_domain%2Fmetaweb_framework
>
> Do people have other thoughts on it?
> - Name: frameworks, modules, toolkits, etc.
> - Handling of web links: bucket (Web Links) or broken out (docs,  
> code, etc.)
> - Other important properties?
> - Projects that should be listed
> - etc.
>
> I'd actually like to try to set this up within the next few weeks  
> if possible.
>
> -jason
>
>
>
> On Aug 14, 2007, at 7:31 AM, Michele Berg wrote:
>
>>
>> Since I currently work at a wiki company, I was thinking of creating
>> a workspace for people who are interested in collaborating on what
>> these guidelines might be.
>>
>>
>> I think a wiki would be a good idea, especially if the content  
>> were tied back to Freebase.  If we do move forward in evolving a  
>> standard, it would be nice to have a central place to keep our  
>> thoughts.  Also, as new people join the discussion, they'd have an  
>> easier way to access the discussion's history, rather than  
>> searching email archives.
>>
>> Michele
>> _______________________________________________
>> Developers mailing list
>> Developers at freebase.com
>> http://lists.freebase.com/mailman/listinfo/developers
>
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers

#!/usr/bin/perl
chop($_=<>);@s=split/ /;foreach$m(@s){if($m=='*'){$z=pop at t;$x=
pop at t;$a=eval"$x$m$z";push at t,$a;}else{push at t,$m;}}print"$a\n";