a few days on. feedback requested

[Doug Tangren]

I've spent a bit more time on a git based approach and am looking for feedback.

# Arbitrary Metadata

I have an example metadata repo I'm testing with here https://github.com/softprops/testmeta with a few modules with minimal metadata

Module metadata can now be arbitrary and nested ( think configurations ) https://github.com/softprops/testmeta/blob/master/metadata/me.lessis/semverfi/0.1.0/module.json#L5-L9

https://github.com/softprops/adept/blob/master/src/test/scala/ManagerSpec.scala#L46-L67 

These get parsed into an ast of types similar to those provided by json https://github.com/softprops/adept/blob/master/src/main/scala/attributes.scala and are accessible via the module interface. Things like configurations and ivy's extra attributes come out of the box as a result.

# Things you can do with Metadata

I'm growing a small interface for what you can do with modules ( https://github.com/softprops/adept/blob/master/src/main/scala/manage/modules.scala#L9-L15 ) 

and metadata repos ( https://github.com/softprops/adept/blob/master/src/main/scala/manage/repos.scala#L4-L9 )

I think this covers most of metadata management. Adding new metadata still needs some extra validation with respect to asserting artifacts provided are resolvable and correctly hashed. 

I'll continue to post progress but I'd like some feedback ( particularly from Mark :) ).

-Doug Tangren
http://lessis.me

[Mark Harrah]

What I would ask you is- what do you think needs to be proven the most? That is, what aspects do we have questions about or are unsure of whether they are a good idea? For example, one question is how many modules can be handled efficiently? Or, do we need a database to index the modules or will just a brute force read from disk + process work for reasonable repository sizes?

So, what do we want to know and how can prototyping help us answer those questions?

In my opinion, the most important thing we can do is to have an empirically backed description of the expected behavior of adept. That is, do what you are doing + record what worked and what didn't in what circumstances.

-Mark

>
> -Doug Tangren
> http://lessis.me