Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 14 01:33
    poulson closed #276
  • May 14 01:33
    poulson commented #276
  • May 14 01:30

    poulson on master

    Update README.md (compare)

  • May 14 01:24

    poulson on master

    added logo (compare)

  • May 10 21:37
    jedbrown commented #276
  • May 10 21:25
    poulson commented #276
  • May 10 21:21
    jedbrown commented #276
  • May 10 17:08
    poulson commented #276
  • May 10 17:03
    tesch1 opened #276
  • Apr 10 13:18
    JM1 commented #275
  • Apr 10 13:16
    JM1 synchronize #275
  • Apr 10 08:56
    JM1 opened #275
  • Mar 06 03:47
    Raviteja1996 closed #274
  • Mar 05 05:46
    Raviteja1996 opened #274
  • Feb 11 21:53
    BenBrock commented #228
  • Feb 11 21:52
    BenBrock commented #228
  • Feb 11 21:51
    poulson commented #228
  • Feb 11 21:50
    poulson commented #228
  • Feb 11 21:45
    BenBrock commented #228
  • Jan 23 23:57
    adambaskerville commented #273
Ryan H. Lewis
@rhl-
it would also seem reasonable to move just the HEAD documentation into the Elemental repository, and copy versions of it out to the website repo as needed
Jack Poulson
@poulson
more important than what is missing is that a huge amount is out of date
I don't like the docs being in the main repo because it clutters the commit history
Ryan H. Lewis
@rhl-
(not to sound crass, but, that is what auto generation is for)
@poulson: not sure what you mean, the documentation is just as important as the code itself.
Jack Poulson
@poulson
perhaps, but it is useful to be able to filter
Ryan H. Lewis
@rhl-
if anything the documentation is more important :)
Jed Brown
@jedbrown
@poulson What do you mean by not wanting docs in the main repo? That sounds like asking for it to be even more out of date.
Ryan H. Lewis
@rhl-
@jedbrown +1
Jed Brown
@jedbrown
By having it in the main repo, the expectation is that docs are updated concurrently with changes to the library.
Ryan H. Lewis
@rhl-
@jedbrown +1
Jed Brown
@jedbrown
Or do you just mean that generated docs shouldn't be checked in?
Jack Poulson
@poulson
certainly the generated docs should not be
Ryan H. Lewis
@rhl-
yeah, no question about that
Jack Poulson
@poulson
Elemental's docs used to be in a doc/ subfolder back when GitHub pages required a separate branch
it caused huge pains
Ryan H. Lewis
@rhl-
i dont understand what github pages have to do with this
Jack Poulson
@poulson
it has been a while since the switch was made to a separate elemental-web page, which was more general and for the whole website
it used to be that the GitHub repo served the docs as well
Ryan H. Lewis
@rhl-
ah, I see
that is not necessary :)
we can use jenkins to update the docs nightly
Jack Poulson
@poulson
there still needs to be a repo for the website itself
and it's useful to have the docs there
Ryan H. Lewis
@rhl-
yeah, that can stay where it is
Jack Poulson
@poulson
unless the website repo is supposed to pull from the main repo
Ryan H. Lewis
@rhl-
you can use jenkins to do all of this
exactly how its setup is somewhat irrelevant
you can compile and copy and commit or use git submodules
Jack Poulson
@poulson
git submodules should be avoided at all costs due to not being supported by GitHub
Ryan H. Lewis
@rhl-
ok, I mean, all I am saying is that its just a small bash script
whatever it is
and it can be stuck in jenkins
Jack Poulson
@poulson
sounds fine to me now that there is a Jenkins
Ryan H. Lewis
@rhl-
is the next release v 0.87 ?
Jack Poulson
@poulson
yes, given the mess around releasing 0.86, let's 86 the 0.86 release
Ryan H. Lewis
@rhl-
want to say we will release Sep 3?
Jack Poulson
@poulson
we should release when we have packages ready
Ryan H. Lewis
@rhl-
debian packages?
Jack Poulson
@poulson
which seems to require ditching ScaLAPACK
which seems to require me implementing a distributed Hessenberg QR
Ryan H. Lewis
@rhl-
ok
I think we should follow a "train leaving the station" model
Jack Poulson
@poulson
METIS and ParMETIS will still cause headaches
Elemental needs its own AMD reorderings anyway
Ryan H. Lewis
@rhl-
I've created the GitHub Milestone, and i'm adding issues.
Jack Poulson
@poulson
thanks!
Ryan H. Lewis
@rhl-
What was the thing you added recently? was there an issue for it?
the D&C SVD?
Jack Poulson
@poulson
something in the middle of my preference to add functionality forever and your desire to release every day is likely the right compromise