Welcome the new maintainer of Loom: Paul Snyder

[Aysylu Greenberg]

I'm pleased to announce that Paul Snyder (@pataprogramming, pataprogramming on Github) has joined me in maintaining Loom. I'm excited for the coming year for Loom, with more excellent contributions accepted faster.

Cheers,

Aysylu

https://twitter.com/aysylu22/status/697751663642284032

[Paul L. Snyder]

On Thu, 11 Feb 2016, Aysylu Greenberg wrote:

> I'm pleased to announce that Paul Snyder (@pataprogramming, pataprogramming

> on Github <https://github.com/pataprogramming>) has joined me in

> maintaining Loom. I'm excited for the coming year for Loom

> <https://github.com/aysylu/loom>, with more excellent contributions
> accepted faster.

Thanks very much, Aysylu, and thanks to Justin for creating Loom and to
everyone who's contributed its lifetime. This library for easily
manipulable, moderate-scale persistent graphs occupies a useful niche in
the Clojure ecosystem.

I'm starting to review the open pull request and issues. If you have
a particular feature that you'd like to see, or a use case that you'd
like to see Loom work toward supporting, please let me know.

One things that I particularly hope to improve is the ability to
easily visualize and interact with your graphs. Graphviz is a nice
starting point, but it's limited to static images.

In previous projects, I've interfaced Loom with JUNG (http://jung.sf.net)
to add interactive, Swing-based graph visualizations. As a library, JUNG
is getting rather stale (its last release was in January 2010), but some
of its facilities and APIs may serve as inspiration for future
directions.

I've pulled some of the interface code out of a previous project, cleaned
it up, and added better support for the Seesaw library for using Swing
from Clojure (http://github.com/daveray/seesaw). This is not likely to
be immediately useful to anyone, but it's a nice proof-of-concept.

You can give it a try from

http://github.com/pataprogramming/loom-jung

There is a short walkthrough on using the library to visualize simple
graphs. Doing anything more complicated will likely require digging into
JUNG's (exceedingly ugly) API, but it's enough to play around with. The
library is also available from Clojars:

[pataprogramming/loom-jung "0.1.0"]

Paul

[Andy Fingerhut]

I had never seen JUNG before.  I've not looked at its implementation at all, but the demos are pretty impressive.  As you say, graphviz is nice for what it does, but I did not realize there was an open source 'graphical graph manipulator' like this.

Andy

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gregg Reynolds]

On Feb 11, 2016 6:19 AM, "Aysylu Greenberg" <ays...@gmail.com> wrote:
>
> I'm pleased to announce that Paul Snyder (@pataprogramming, pataprogramming on Github) has joined me in maintaining Loom. I'm excited for the coming year for Loom, with more excellent contributions accepted faster.

Your Readme doesn't even bother to say what loom is.

[Paul L. Snyder]

Hi, Gregg,

Thanks for pointing out an area where additional clarification would be
helpful to potential users of Loom.

Who is the 'you' that this criticism is intended to address? Aysylu, who's
been serving as maintainer for this library over the last years? Justin,
who originally created it? The over two dozen contributors who have helped
build its functionality? Suggesting that they didn't "even bother" with
something is, frankly, rude and unproductive.

I'm happy we don't see much of this sort of casual disrespect in the
Clojure community (with the exception of occasional bad actors on the
mailing list). The worst of what we do see is, largely, aimed at those who
contribute the most: the team that maintains Clojure itself.

People who are willing to invest their time to make and share useful tools
are a resource. They should be allowed to direct their energy toward making
those tools better, rather than having it drained by jerky interactions.
Whether we find a project personally useful or not, we owe Open Source
authors, at a minimum, politeness. This is at least partially in our own
interest: we want them to keep making those tools, rather than burning out
and switching to a more rewarding activity.

Here's an article on framing feedback in a less confrontational and
accusatory manner.

http://personalexcellence.co/blog/constructive-criticism/

"Thanks for sharing Loom. There's a lot of information in the README, but
I found it difficult to figure out what the library actually does. It
would be helpful to have a concise, up-front description of its purpose."

Regards,
Paul

[Ghadi Shayban]

You're going to be a great maintainer, Paul.

[Rafik NACCACHE]

I want to thank you guys for this library. I use it in milestones,my project scheduling library (https://github.com/turbopape/milestones) to detect cycles in tasks precedence graph. Keep on the great work, and all the best for the maintaibers' team!

[Julio Barros]

+1