text:
An eclectic reflection about life in the present. Photography. Brief writings.
The a.c. fellas worked all day, a long day. I got to sit and answer questions. It was awful. But the fellas were nice guys, very polite to one another. They were Hispanic and spoke in English around me but in Spanish to one another. It was tough, hot work, but they never cursed nor complained. Rather, they laughed and joked and helped one another along. They had that cowboy mentality, or should I say vaqueros.
By seven o'clock, I had a new a.c./furnace.
The house seemed to take a long time to cool down. My gut was in spasms. What if. . . ?
It was 64 outside this morning when I woke up. Not a good test. I worry, of course.
Oh, and I was disabused of the idea that I had 0% financing. It was the fellow who owns the camera store who wised me up. He said they had the same deal on cameras. It is through a company called Equiscam or something. It is really a deferred interest plan, he said. Make sure you pay every month early. If you miss one payment, they charge you all the interest at once. Whoa! I am not that good at keeping up with pay dates. I will need to get to the bank and set up autopay as soon as I can.
Maybe right after I rush to the post office to mail my tax extension form.
I was at the camera store to pick up the film I took in from my old Diana and Helga cameras. How long ago did I do my surf series? Seven years? The film in that leaky old plastic camera had pictures on it from then. That is why, I guess, you see the image of the backing paper on the photographs. Light leaks over the years. Q said they looked cool, so I will trust that.
I loaded three Diana and one Holga camera(s) up with film the day I shared the woman's Diana images with you. I haven't shot a single picture with them yet. I might, though. I mean. . . I could.
There are so many things I might do.
Posted by cafe selavy at 8:18 AM
Blog Archive January (15) December (31) November (27) October (31) September (30) August (31) July (33) June (32) May (33) April (35) March (42) February (30) January (33) December (34) November (31) October (27) September (19) August (29) July (21) June (23) May (23) April (22) March (23) February (24) January (20) December (7) October (6) September (30) August (31) July (30) June (11) March (25) February (25) January (26) December (31) November (29) October (28) September (25) August (28) July (25) June (28) May (24) April (21) March (29) February (23) January (29) December (31) November (28) October (23) September (26) August (30) July (27) June (28) May (27) April (28) March (25) February (27) January (28) December (28) November (30) October (24) September (23) August (28) July (29) June (28) May (20) April (27) March (32) February (28) January (10) June (5) May (28) April (23) March (26) February (23) January (18) December (4) November (7) October (3) September (41)
Inventory of Mortality
Photography is the inventory of mortality. . .
"The only thing that ever stood between me and success was me."
"You're not a moron. You're only a case of arrested development."
- Chapter 6, The Sun Also Rises, Ernest Hemingway
Tiziano Terzani
"The truth is, at fifty-five one has a strong urge to give one's life a touch of poetry, to take a fresh look at the world, reread the classics, rediscover that the sun rises, that there is a moon in the sky and that there is more to time than the clock's tick can tell us."
"This whole world's wild at heart and weird on top"
Barry Gifford, Wild at Heart
Secret About A Secret
A photograph is a secret about a secret. The more it tells you the less you know.
I am, I am
Blind moil in the earth's nap cast up in an eyeblink between becoming and done. I am, I am. An artifact of prior races.
Suttree
The photograph isn't what was photographed, it's something else. It's about transformation. . . . There is a transformation, you see, when you just put four edges around it. That changes it. A new world is created.
Gary Winnogrand
Life is short,
But by God's Grace,
The Night is Long
Safe Passage
Here I am, safely returned over those peaks from a journey far more beautiful and strange than anything I had hoped for or imagined - how is it that this safe return brings such regret?
A Generation of Swine
"What do you say, for instance, about a generation that has been taught that rain is poison and sex is death?. . . [T]here is not much left except TV and relentless masturbation."
Dr. Hunter S. Thompson
"If you try to probe, I'll lie to you. Seventy-five percent of what I say in interviews is false. I'm like a hen protecting her eggs. I cannot talk. I must protect my work. Introspection is bad for me. I'm a medium, not an orator. Like certain oriental and Christian mystics, I think the 'self' is a kind of enemy. My work is what enables me to come out of myself. I like what I do, not what I am. . . . Do you know the best service anyone could render in art? Destroy all biographies. Only art can explain the life of a man--and not the contrary."
Orson Welles, 1962
" 'Late work.' It's just another way of saying feeble work. I hate it. Monet's messy last waterlilies, for instance — though I suppose his eyesight was shot. 'The Tempest' only has about 12 good lines in it. Think about it. 'The Mystery of Edwin Drood.' Hardly 'Great Expectations,' is it? Or Matisse's paper cutouts, like something from the craft room at St. B's. Donne's sermons. Picasso's ceramics. Give me strength."
"Engleby"
Sebastian Faulks.
It is awfully easy to be hard-boiled about everything in the daytime, but at night is another thing."
What's Remembered
"The only things that are important in life are the things you remember."
"One shudders at the thought of the meaninglessness of life while at the same instant. . . one love life so intensely that tears come into the eyes."
"The eye sees only what the mind is prepared to comprehend."
Joyce's Lament
"History is a nightmare from which I am trying to awake."
Stephen Dedalus, "Ulysses"


You can subscribe to Garland Magazine for only $AUD 40 a year. This unlocks a year's worth of exclusive content, including the specially commissioned Quarterly Essays. These are thoughtful articles on a beautiful handmade object with an intriguing story to tell. Your subscription helps to support the Garland platform that aims to support the welcoming conversation between creative practices in our region. You will also be able to access the entire issue in e-book form.
You can subscribe by bank transfer if you prefer using this form.


We are grateful to Polyarix and its founder Ilya Kireev for the cooperation. We have been working with Polyarix for over 4 years. Over this time, more than 15 websites have been developed and more than 150 projects on animated advertising of Flash and HTML5 / Js technologies have been created. We recommend Polyarix as a responsible and reliable partner.


text:
Q: Converting from excel to pdf in PHPSpreadsheet without ruining design/style I tried exporting my PHPSpreadsheet as a PDF. What I did was setting the header like:
header("Content-Disposition: attachment;filename=hello world.pdf");

and the $writer like this:
$writer = new \PhpOffice\PhpSpreadsheet\Writer\Pdf\Mpdf($spreadsheet);
$writer->save("php://output");

The rest of my code stays the same as for exporting as XLSX. It seems to not like the styling commands and also imports the cells where there is no text. An example of how I create info in a cell for Excel is like this:
$sheet->setCellValue('A16', $activitiesCount)->getStyle('A16');
$sheet->getStyle('A16')->getFill()->setFillType(Fill::FILL_SOLID);
$sheet->getStyle('A16')->getFill()->getStartColor()->setARGB('d9e6fc');

Here is the original in excel:

This one exports fine if I save it as PDF directly from excel itself. But when I try to do it with my code, this seems to be the result:

As you can see its getting really messy. Does it mean I have to program it in a another way for PDF? I thought it was going to be easy to change between those to.
PS: Dont mind the name differences between the pictures. I tested something in DB to see how it scales when name is really long. It wasnt pretty, let me tell you.

A: This isn't much of an answer, but if you read the documentation you will see a note:

Please note that PDF file format has some limits regarding to styling cells, number formatting, ...

You might have better luck trying a library other than mPDF. From the same page:

The different libraries have different strengths and weaknesses. Some generate better formatted output than others, some are faster or use less memory than others, while some generate smaller .pdf files

A: $extension = 'Mpdf';
$writer = new \PhpOffice\PhpSpreadsheet\Writer\Pdf\Mpdf($spreadsheet, $extension);

if (empty($report)) {
    $reportData['listing_id'] = $id;
    $reportData['year'] = $y;
    $reportData['month'] = $m;
    $reportData['excel_name'] = 'r_' . $id . '_' . $y . $m . '_' . time() . '.pdf';
    $report = ListingReport::create($reportData);
} else {
    $report->update($reportData);
}

$filePath = public_path("files/report/$report->excel_name");
$writer->save($filePath);
$headers = array(
    'Content-Type: application/pdf',
);

A: I am facing the same issue as you, and I found out it is actually the cell styling issue (not sure what PHPSpreadsheet is doing while reading the cell content and settings). and my workaround is select those unintentional bordered cells and select No Border on them, then the result comes out as expected.
I found my workaround when playing with cell border.
Hope it helps !

redpajama_set_name: RedPajamaStackExchange


text:
You have not saved any jobs yet
Clinical Lead
Job Title: Clinical Lead
Salary: £42,414 - £47,798
Salary: MAC-UK Salary band 8a £42,414 - £47,798
Hours: 15 to 22.5 hours/2 to 3 days per week with flexible working (hours are flexible depending on successful candidate's preference, but must be worked between Tuesday and Friday)
Location: Old Street, with occasional travel to projects around London
About MAC-UK
We're here to effect positive change with, and for, excluded young people such as those in or leaving care, or at risk of involvement in criminal behaviour and/or exploitation. Taking a public health approach, we work alongside young people to change the social and environmental factors that expose them to risk. Our vision is to transform mental health delivery, addressing inequality of access so that it's possible for every excluded young person to shape the services that are there to support them, working together to co-produce mental health solutions fit for the 21st Century.
Clinical Lead is a senior clinical role at MAC-UK, responsible for supporting with development and implementation of clinical governance and operations, primarily through staff clinical supervision. The role sits within MAC-UK's Dissemination team, which is key to the success of MAC-UK's long-term objective to transform mental health services for excluded young people.
To work primarily through supervision of project leads and senior staff to ensure a high quality clinical function across the organisation that is in line with the strategic objectives
To support the fidelity to the INTEGRATE approach across projects, partnerships and services
To support the Senior Leadership Team (SLT) to facilitate MAC-UK's systems for recording and sharing learning across MAC-UK
To ensure the provision of youth participatory, high quality clinical care, ensuring that young people are at the heart of the design and delivery of services
To act as one of the MAC-UK Safeguarding leads; to support staff during working hours and in the out of hours rota in line with MAC-UK's 'Out of Hours' protocol if needed
For further information and to apply please visit MAC-UK's website http://www.mac-uk.org/current-vacancies.
The closing date for applications is 5pm on Monday 5th November.
MAC UK
Circa £45,000 depending on experience
Band 8A
Salary: £40,792-£48,677 per annum
The British Psychological Society is the representative body for psychology and psychologists in the UK. We are responsible for the development, promotion and application of psychology for the public good. https://www.bps.org.uk/about-us
Site essentials
CPL publishes Jobs in Psychology on behalf The British Psychological Society. For more information on advertising please contact:
Kai Theriault
Tel: +44 (0) 1223 378 051 or email kai.theriault@cpl.co.uk
All content copyrighted CPL (Cambridge Publishers Ltd) © All rights reserved

redpajama_set_name: RedPajamaCommonCrawl


MARION COUNTY, Alabama – A 462-acre industrial park off the future Interstate 22 stands as a symbol of cooperation in this northwest Alabama county, and officials believe that this teamwork approach will help the region along the state's newest superhighway land new jobs and investment.
Until recently, the Interstate 22 Gateway Industrial Park had a split personality. Actually, the site held two adjoining industrial parks, one belonging to the city of Winfield and the other to the adjacent town of Brilliant. Prospects viewed the parks as disconnected and separate, making them virtual competitors.
"It was always awkward that we had two parks of similar size that share the same roadway access and utilities yet were in two different communities," said David Thornell, president of the C3 of Northwest Alabama Economic Development Alliance, a partnership uniting Marion, Fayette and Lamar counties.
Not any longer. The consolidation of the two community-owned sites into the Gateway Industrial Park has created the largest industrial site along I-22's route in Alabama, making the location more suitable for large projects and streamlining marketing efforts. Asking prices at the site have been reduced to $9,500 an acre to make the park even more attractive.
"This is a great example of cross-community cooperation," Thornell said.
Gateway Park flanks three sides of the Exit 30 interchange on the future I-22 (now officially called Corridor X, linking Birmingham and Memphis), and the site is prepared for development, Thornell said. Access roads and utilities are in place, and two large fueling stations and a Hampton Inn stand nearby.
Thornell said Gateway Park is being marketed to auto parts makers because of its proximity to the Toyota assembly plant near Tupelo and the Mercedes-Benz plant in Tuscaloosa County, both about an hour's drive away. He thinks the park also would be ideal for distribution operations, metal fabricators and the makers of construction and farm equipment or recreational vehicles.
"All the park needs is for a company to call it home," Thornell added.
What's going on in Marion County aligns with the goals of a new rural economic development push in Alabama that calls for a greater level of cooperation and a regional teamwork approach to overcome obstacles facing smaller communities competing for projects. The Economic Development Association of Alabama and the Alabama Department of Commerce are spearheading the strategic approach.
Steve Foshee, chief executive of Tombigbee Electric Cooperative and chairman of C3's strategic planning committee, said having neighboring industrial parks at Exit 30 reflected what some call "Friday night football syndrome" – in essence, the two local teams were lined up and going head to head.
Before that happened, though, the problem was brought home when an overseas industrial prospect came calling to inspect the Winfield and Brilliant sites off Alabama Highway 129 at Exit 30.
"They couldn't understand how we went from one town to another. You could see the confusion in their eyes. You don't want confusion at that stage. It was a lesson learned," Foshee said.
The industrial prospect didn't pick Marion County. Later, in strategic planning sessions, the dual identities of the Winfield and Brilliant sites were pinpointed as a key shortcoming, underscoring the need to unify them as a single entity, Foshee said. A consultant brought in by C3 made the recommendation.
Leaders in Brilliant, a town with around 730 residents and a coal mining heritage, and Winfield, a city of about 5,000 known for its popular Mule Day festival, embraced the idea. The I-22 Gateway Industrial Park was born.
Thornell and Foshee said the spirit of cooperation that linked the two community-owned industrial parks has been growing in the region since the founding of the C3 organization more than three years ago. C3 was designed to provide a single point of contact for prospects and create an economic development brand for Marion, Fayette and Lamar counties.
Thornell believes the cooperation that made the I-22 Gateway Industrial Park possible should send a strong message to prospects, site selection consultants, regional commercial real estate agents and others that C3 communities are working together as a team.
"Because we work together, we create a more inviting and desirable environment to attract prospects and to support the success of businesses that consider locating here," Thornell said.


Last modified on 2018-08-08 20:12:15 GMT. 0 comments. Top.
PCRG's partnership with the National Community Stabilization Trust makes foreclosed properties available for purchase at a discount to our member organizations and their partners. When staff saw a property in Observatory Hill become available through the program, PCRG contacted NSLC who connected us with the OHI Board of Directors. The board realized that the property was in their area of focus – on Perrysville Avenue, only a few blocks from the business district, close to their own renovation projects on Bonvue STreet. Both the OHI Board and NSLC requested that PCRG work with a neighborhood resident, William Oberst, to ensure the property was redeveloped.
William Oberst is a resident of Observatory Hill who has renovated at about eight houses in the area, of which four have been located on Perrysville Avenue. The house needed a complete rehab, including a new roof, new plumbing, new electrical, and a completely rehabilitated interior, including new floors, drywall, and more. The house was also converted from a duplex into a single-family home. "Renovating the houses has been a passion of mine, and a win-win for the community," Oberst said. With the completion of the house, Perrysville Avenue gains another beautiful property, neighbors' property values will increase, and one more vacant house will be inhabited again.
PCRG works with financial institutions to connect our members to opportunities to purchase houses in their neighborhoods. Those homes will be renovated and then leased or sold to qualifying individuals. If you're interested in participating in our program, please contact Justin Belton at jbelton@pcrg.org or call the PCRG office at 412-391-6732.
Last modified on 2018-07-26 15:48:36 GMT. 0 comments. Top.
PCRG held its first Developers' Roundtable on June 29th, 2018, with the purpose of understanding affordable housing developers' concerns related to utilizing the Low-Income Housing Tax Credit (LIHTC). The Roundtable took place at PCRG and consisted of numerous developers from the Pittsburgh area, as well as a call-in from an outside developer. The purpose of the meeting was to determine the inefficiencies in utilizing the 4% LIHTC, which is a non-competitive tax credit that is allocated to investors when affordable housing is financed by federal government issued tax-exempt bonds.
The LIHTC program is used to leverage private capital to finance construction and rehabilitation of affordable housing. Since its inception in 1986, the LIHTC program has built of 3 million affordable housing homes and leveraged over 100 billion dollars in private capital for quality affordable housing. Experts consider the LIHTC program to be the most successful affordable housing production and rehabilitation program in U.S. history. The tax credits are either allocated as 9% or 4% credits. The 9% credits are used exclusively for construction of new affordable housing, while the 4% credit is used for rehabilitation and construction. The 4% LIHTC is an important tool in the rehabilitation of Pennsylvania's ageing housing stock and construction of new affordable housing. However, according to the Pittsburgh Affordable Housing Task Force, the 4% credit is highly underutilized in Pittsburgh.
The 4% LIHTC is allocated by the Pennsylvania Housing Finance Agency (PHFA). The PHFA is tasked with, among other things, allocating the 4% and 9% LIHTC. The PHFA recently posted their draft Qualified Action Plan (QAP) for 2019-2020. The QAP explains the requirements and grading criteria for dispersing the 9% and 4% credits. Using the recommendations from the Roundtable, PCRG drafted a public comment to the proposed regulation. Among the topics covered were streamlining the 4% underwriting process, local administration of the tax credits, income averaging and Transit-Oriented Design (TOD). A copy of the comment is attached below. PCRG is excited to continue working with local developers to advocate for progressive and efficient building strategies/regulations to increase affordable housing building yield in Pittsburgh.
The Pittsburgh Community Reinvestment Group (PCRG) is a coalition of over 60 community/economic development corporations and community/neighborhood based organizations, which are located in western Pennsylvania, the City of Pittsburgh and in urban-core communities in Allegheny County.
PCRG's leadership seeks to develop tools and resources for residents that create communities of choice where all are welcome, where there is quality affordable housing, convenient/regular transit service, and access to capital that can be used to drive wealth development.
After a review of the QAP for 2019-2020, we offer the following suggestions to help grow Pennsylvania's affordable housing inventory. There is a focus on Allegheny County, with the understanding that over two-thirds of the urban allocation of 9% tax credits are being allocated to Philadelphia.
The 4% low income housing tax credit is an important tool in the rehabilitation of Pennsylvania's ageing housing stock and construction of new affordable housing. According to the Pittsburgh Affordable Housing Task Force, the 4% credit is highly underutilized. PCRG's following recommendations regard formulating more efficient ways to underwrite and review the 4% tax credit. The following also addresses PCRG's support for the proposed income-averaging rule change and implementing language in the 2018 QAP that incentivizes combining 4% and 9% tax-credits to leverage project funding.
Streamline the current 4% tax credit process by creating separate underwriting criteria for 4% credits: The current tax-exempt bond financing system is constraining the use of 4% credits. The current 4% credit underwriting in Pennsylvania requires substantially the same underwriting process as the 9% credit, when the 9% credit supplies more than twice as many credits to investors. Other states treat 4% and 9% credits differently during the underwriting and application process. Ohio is a good example of one of these states. Ohio requires almost all 4% underwriting documents to be submitted on the submission date, while 9% underwriting documents are often due at different times, requiring certain documents to be submitted with the proposal and others during the final submission. This often leads to 9% credit applicants having to resubmit certain documents at time of proposal and final submission, which 4% credits do not have to do. The Ohio HFA also does not score 4% credit applications like they score competitive 9% credits. The 4% credit application simply requires that all applications meet certain threshold criteria, making the process simpler and easier to navigate. Ohio treats development costs and developer fees differently as well, which in turn incentivizes the use of the credit. For example, Ohio does not place a total development cost limit on their 4% credits, only stating that the OHFA "reserves the right to reject any application it deems excessively costly." It also does not place a cap on developer fees for 4% credits, stating that developer fees can be 25% of the eligible basis, though excess of 20% must be deferred or reinvested (pages from the QAP are attached herewith). Kentucky is another state with a higher developer fee cap, allowing for a maximum 20% developer fee for 4% credit transactions. Finally, the Ohio HFA allows for 4% applications to be accepted on a quarterly basis, instead of the once a year application. This allows for continuous allocation of credits over the course of the year, which increases building yield and incentivizes the continued use of the credit. Washington DC also has a yearlong rolling application date. PCRG believes that Pennsylvania should follow Ohio, Kentucky and DC's lead in allowing for certain 4% credit underwriting that is less stringent than 9% underwriting. This will encourage developers to undertake projects with the 4% credit and increase overall building yield.
Allocate authority to local Redevelopment Authorities to review/approve 4% tax credit applications: Currently, 4% credit applications are reviewed by the state PHFA as part of the open application period, once a year. This leads to a backlog of tax-exempt bond applications that qualify for 4% tax credit consideration. We recommend that the state PHFA allocates authority to review these non-competitive applications to qualified local redevelopment authorities that have the capacity to conduct the review. This will decentralize the process in multiple areas of the state, while decreasing 4% application decision wait-times. States such as Maryland and Minnesota allow for review of 4% tax credit deals by local authorities while Massachusetts' HFA works closely with two local quasi-governmental agencies to allocate their tax-exempt volume cap. PCRG understands that certain PHFA offices in Pennsylvania do not have the capacity to review these applications. However, local redevelopment authorities do. PCRG believes that decentralizing the process will allow for an open application cycle, while increasing productivity and efficiency. This will also allow applicants to create more units over the course of the year.
Consider including language in QAP regarding combining 9% and 4% tax credits to increase funding: PCRG urges the PHFA to consider including language in its 2019-2020 QAP regarding combining 9% and 4% tax credits for financing, also known as "twinning." Twinning is currently being used in states such as Virginia to close financing gaps in projects with higher unit counts, and Washington DC and Maryland are just now considering projects with this financing. It is also allowed for/encouraged in a number of other states, including California, Colorado Connecticut, Massachusetts, Minnesota, Rhode Island, Tennessee, Texas and Washington (other states do not necessarily prohibit it). Virginia, in particular, encourages combined financing by assigning additional points to applications for mixed tax credit projects. Specifically, more points are allocated for projects financed by tax-exempt bonds, based on what percentage of total units are financed by the bonds. For example, projects where >50% of units that are financed by tax-exempt bonds receive more points than developments where >30% of units are financed by tax-exempt bonds. We believe that this system can be used to incentivize using 4% bonds and allows for more creative financing structures, specifically in larger unit developments that would not be economically feasible using only 9% credits. Other states' use of twinning has shown that these transactions can be complicated and are not necessarily appropriate in every 9% credit deal. However, we believe that twinning language should be considered in the QAP and utilized in specific cases to leverage more funding to allow for higher unit counts.
Income Averaging (Pg. 19): PCRG supports the PHFA's decision to include income averaging as a third-minimum set-aside election in the 2018 QAP draft. The Consolidated Appropriations Act of 2018, which created the income averaging election, does not require states to offer this third set-aside option. However, income averaging will allow for more units between 60% – 80% AMI, while at the same time increasing the economic feasibility of creating deeply affordable units, which are in high demand. This will also allow for a greater diversity of tenants at different income levels in tax credit properties. There have been some concerns among finance experts that a new set-aside option will require additional oversight and lead to compliance missteps. PCRG understands these concerns but believes that the benefits of income averaging far outweigh the potential risks. Income averaging allows for more creative financing structures than the rigid minimum set-aside elections (20-50, 40-60) and can be used to finance projects that previously would not be economically feasible.
Transit-Oriented Design "TOD" – The Agency currently may award two (2) points to developments located within one-half mile of a completed or planned public transportation fixed route stop. PCRG strongly supports and encourages the agency to further reinforce Transit enriched sites. Most low income and working class individuals/families rely on readily available transportation for access to their work, public services, and education centers. Transportation is therefore vital to residents' independence. PCRG suggests that the site rating area of the QAP be further weighted. In the past, PCRG has seen Pittsburgh projects awarded credits that are located in low transit corridors that isolate the tenants that need it most.
We hope that the suggestions provided help the 2019 QAP become stronger in advancing true housing affordability- through changes to the 4% tax credit system, income averaging and transportation. Thank you for your consideration and please do not hesitate to contact us with any further questions or information.
Last modified on 2018-07-27 14:56:50 GMT. 0 comments. Top.
City Council has unanimously approved a plan that Mayor Bill Peduto says "will help heal one of Pittsburgh's worst efforts at urban renewal, when decades ago city planners separated the Hill District from Downtown and cut the lifeblood from one of our most historic communities." More than $26M has been earmarked for an ambitious plan to build a park, install public art, and improve pedestrian access over three acres between downtown and the Lower Hill. Also included in the plan is an improvement to storm water management infrastructure. The park would be placed in one of the most nerve-wracking intersections in the city – for pedestrians, drivers, and bikers alike – at the Washington Place and Centre Avenue intersection of the Crosstown Boulevard.
This decision coincides with a plan from the Pittsburgh Penguins to spend $450M to create residential, retail, and office space in the former Civic Arena site – in the wake of increased calls for more affordable housing in Pittsburgh. Whether or not the Penguins will move ahead with the affordable housing aspect of this plan is yet to be seen as the Penguins were not selected to receive a Low Income Housing Tax Credit (LIHTC) for the project. Of the planned 935 units, 20% were to be affordable, but this was contingent on receiving 9 tax credits. The mayor's Chief of Staff, Dan Gilman, says that despite this setback, the city and the Penguins are committed to building affordable housing.
In total, $26,440,000 in funds has been set aside for a plan that won't begin construction until early 2019, following a public bid for the construction contract, according to the Sports & Exhibition Authority (SEA). With an estimated 27 months of construction, the park would not be open to the public until March or April of 2021 at the earliest.
Last year, Marimba Milliones of Hill Community Economic Development Corporation stated that the plan for the intersection is "essential to pursuing goals laid out in a Lower Hill redevelopment plan created in 2014 by her organization, Hill District residents, the Penguins and others." Those goals include empowering minority and women owned business, honoring the cultural legacy of the Hill District, and creating work for the Hill's residents.
Using the Pittsburgh Historic maps tool, one can see the progression of the Lower Hill from 1957 to 1967 to the present day. From a small but bustling neighborhood filled with small businesses and family homes to a space dominated by a single white sphere to a vast parking lot in the span of 54 years, the Lower Hill has seen massive change. Part of that change has been the economic decline that ravaged the Hill following the turn of the century. It would be unfair, of course, to say that the Civic Arena brought the economic decline to the Hill, but the demolition of hundreds of homes and business certainly encouraged the decay. More than 8,000 people and 400 businesses were displaced for the promise of reinvestment. Promises of a cultural hub and "urban renewal" came with plans for opera house and symphony hall, multiple arenas, theaters, an art museum, luxury apartments, hotels and offices that were never completed. Further division came with the construction of the Crosstown Boulevard/I-579. Former residents of the Lower Hill cited the loss of landmarks like St. Peter's Church, banks, and Victorian era homes as particularly heartbreaking because they represented social and historical capital.
With the scars on the Hill still healing, it should come as no surprise that Pittsburgh residents, spefically those in the Hill, are hesitant. There are decades of generational trauma – borne of families and institutions being uprooted for unfulfilled promises – to wade through. However, it is the hope of many that this cap park, in concert with the Penguins' plan to restore the former Civic Arena site, will begin a process to restore the Hill District and undo the decades of damage caused to a neighborhood and a city.
Last modified on 2018-07-27 14:03:36 GMT. 0 comments. Top.
Last modified on 2018-07-27 12:18:22 GMT. 0 comments. Top.
Keeping this in mind, it is clear that it is essential to update assessment areas to reflect the current digital age – we must include non-traditional lending institutions and technological advances when evaluating CRA activities. Regulators should be given broader assessment reach to ensure accurate reporting. On the other side of the coin, we must not lose focus on physical place and the branch system. Branches are still crucial aspect of bank lending, investments, and financial services.
In this modern era, technology makes banking possible for every strata of society. The relative ease of access and affordability of technology provides unparalled access to banking and its benefits. In Pittsburgh, for example, there are a number of national banks providing services to our local markets, delivering mortgage lending and other key services, and capturing up to 10% of the market – with no obligation to reinvesting in our communities under the CRA. It is our hope, as the Federal Reserve seeks comment on the CRA, that they will strongly consider the recommendations put forth by PCRG, as well as those comments submitted from the entirety of the community development and banking sectors.
Fintechs - computer programs and other technology used to support or enable banking and financial services.
Last modified on 2018-07-27 14:04:30 GMT. 0 comments. Top.
In southwestern Pennsylvania, long-time residents are familiar with outsider's stigmas about how Pittsburgh continues to cling to its dirty, industrial legacy, with smokestacks ejecting clouds of billowing, toxic chemicals for miles and miles on the City's riverfront and lingering smog tinting the air. For those of us not originally from Pittsburgh, like myself, it's difficult to get people who have never visited the city to re-imagine the city and reform their idea of what Pittsburgh looks like today. Sure, it's frustrating to continuously explain to people that Pittsburgh isn't like it once was but is expected considering Pittsburgh's history is deeply entwined with industrial and commercial development, including some of the most notorious industrialists like Andrew Carnegie, Henry Clay Frick, Andrew Mellon and George Westinghouse.
At the turn of the 20th century, Pittsburgh's smoky pollution and toxic air was seen as a sign of prosperity and evidence of a thriving local economy. Today, Pittsburghers spend time lamenting on the city's past and the impact of deindustrialization on Pittsburgh and surrounding municipalities. Gone are the days of breathing toxic air and wading in the rivers despite the presence of sludge and chemicals – but has Pittsburgh truly separated itself from the past industrial practices and lax environmental standards?
mean air quality issues have disappeared.
Between 2009 and 2016, U.S. Steel paid fines to the Allegheny County Health Department totaling close to $4 million. The production of coke continues to be one of the dirtiest jobs in the steel industry and Clairton happens to have the largest coke plant in North America operating 10 batteries of ovens and producing about 4.3 million tons of coke annually . Not only is U.S. Steel's Clairton Coke Works the largest coke plant on the continent, but its environmental compliance track record should be unsettling to residents in Clairton and surrounding communities: data provided by PennFuture estimates that the facility committed more than 6,700 air pollution violations in a three and half year period  and Clairton Coke Works is classified as a Title V source with other major local and national polluters established by the federal Clean Air Act. Poor air quality, particularly resulting from the increased presence of particulate matter 2.5 and ozone, have been linked with adverse health effects including being at a higher risk of cancer, heart disease, nervous system damage, and breathing problems. Allegheny County continues to be classified as a nonattainment area – a geographic area that is unable to comply with the federal air emission standards – for ozone, particulate matter 2.5, sulfur dioxide, and carbon monoxide.
In Pennsylvania, the County Health Department is the local agency responsible for overseeing facility compliance, air quality monitoring, and enforcing the Clean Air Act. To enforce the Clean Air Act locally, the Allegheny County Health Department established an air quality program – which has been in existence for 26 years – including the Clean Air Fund that companies pay into when they violate their air permits. Over the last few decades, funds from the Clean Air Fund have been used for a variety of improvement projects to benefit Allegheny County communities, including a study of diesel fumes Downtown ($860,000 in 2011) and solar panels at CCAC ($400,000 in 2015). Currently, Allegheny County has around $11.8 million in the Clean Air Fund and on average, the fund accrues an additional $1.3 million annually. At this time, the Allegheny County Health Department is advocating using these funds towards renovating one of their offices', but environmental advocacy organizations, including Group Against Smog and Pollution (GASP), are not in agreement on how these funds should be used since it's questionable how this benefits residents and communities.
In February, an audit conducted by the EPA found that the Allegheny County Health Department was behind on 13 out of 32 permits for Title V pollutions sources, with 10 permits already being expired and past their year-and-a-half review period, and three never even being issued to companies. If the agency responsible for air quality monitoring and oversight is falling behind on their permitting duties and not holding polluters accountable, where does that leave residents?
Changing the Environmental Justice Standards, to what end?
After conducting a nine-stop listening tour in 2017, the state Department of Environmental Protection recently announced that for the first time since 2004, policy changes would be made to Environmental Justice standards increasing the number of people, to around 1/3 of Pennsylvania's total population, who are considered to live in an environmental justice area.
Poor and minority communities often face the worst environmental conditions as a result of nearby industrial development facilities – including landfills, incinerators, coal mines, and coke works – notorious for polluting, but mostly because they lack the financial resources necessary to battle these cases in court. Without effective communication, education, information, and engagement with marginalized people, the updated Environmental Justice policy won't make enough of a dent on its own.
Ultimately, developing, updating, and enforcing an environmental justice policy in Pennsylvania is positive, but there are a lot more subtle intricacies influencing how it functions that were not updated. During the DEP's statewide listening tour about Environmental Justice issues last year, dozens of requests were made for additional oversight of the Marcellus Shale industry and despite these requests oil and gas well permits were not added to the list of environmental justice trigger permits due to time frame issues. In the City of Pittsburgh, fracking is not legally permitted but there are a number of well sites in Allegheny County and other surrounding counties in Pittsburgh's metropolitan area.
Figure3 & 4: Top Ten Polluters in Allegheny County shown on the left, PennEnvironment  (includes Cheswick Power Plant owned by NRG Energy, Clairton Coke Works owned by U.S. Steel, Harsco Metals, and BPI Inc. – McKees Rocks PA Plant). On the right, FracTracker uses an interactive tool to show current Environmental Justice areas (2015 definitions) and surrounding well sites.
With the state DEP and Allegheny County Health Department both making commitments to modernizing policies and changing up status quo practices, this is a huge opportunity for southwestern Pennsylvania to step up and set an example for other cities facing similar environmental challenges. It isn't a coincidence that more than half of the top ten polluters in Allegheny County fall into currently designated Environmental Justice areas, but a strong will to enforce policies, both at the local and state level, is very much needed to hold these companies accountable.
For more information on this newsletter, please contact Adrie Fells, AmeriCorps Outreach VISTA, at afells@pcrg.org or (412) 391-6732 ext. 211.


text:
Phoenix Nightly Builds Now Available
Thursday September 5th, 2002
Nightly builds of Phoenix are now available for download from ftp.mozilla.org. Builds are currently only available for Linux and Windows.
Phoenix (formerly known as mozilla/browser) is a redesign of the Mozilla browser component. It is not related to Project Piglet (also previously known as mozilla/browser), which was forked from pre-Phoenix mozilla/browser code.
Thanks to Asa Dotzler for the news.
UPDATE! Also check out the Phoenix project page which has some more information about the project.
#1 played with it today.....
by whiprush
Thursday September 5th, 2002 7:55 PM
looking good, lean and mean ...
I love the Preferences Dialog .... a huge improvement.
#3 Re: played with it today.....
Please note that the preferences dialog is **under construction**. Some prefs don't work at all or properly. The "Navigator" panel is probably temporary (if not, it will certainly be renamed). And all your favorite geeky prefs will be making a comeback in a forthcoming Advanced panel.
I _like_ it nice and simple, I hope you guys don't go too nuts in there, the 'normal' mozilla preferences is getting out of control.
It will be as simple as it is now (simpler, even, once we have large icons for each panel instead of the current tree). I'm just reassuring others that we intend to keep more prefs, but stick them in the soon-to-be-redesigned Advanced panel (a scrolling tree, like in IE).
#31 Re: played with it today.....
by GAThrawn
Friday September 6th, 2002 7:28 AM
I just hope you'll be setting them out better than IE. There never seems to be any real sense to IE's long list of advanced prefs, they all just seem to be added in in the order that some programmer thought of them, consequently I always have to scroll up and down the list two or three times to find anything.
In a way Moz's tree style for the advanced prefs would be better.
#58 Dammit
by PsychoCS
Sunday September 8th, 2002 1:59 PM
I HATE the MSIE prefs interface. I guess I'm a real minority liking the current Mozilla setup which is very well organized by comparison and of course looks better.
by WillyWonka
The fonts portion is still terrible. No room for a preview of your changes. :(
#60 It's pretty good...
by MozSaidAloha
Monday September 9th, 2002 1:22 AM
I've played with Phoenix a bit and it looks very promising. I have one question: Will Phoenix replace Navigator as we know it?
#2 I miss...
by frogfarm
...the old README.
"Q8: I don't like the mozilla/browser process! This sucks! I'm never going to contribute to Mozilla again!"
"Oh no, please, don't go, whatever shall we do without you."
#6 Latest Builds?
by amutch
Why does the "Latest Builds" button in Phoenix go to the latest builds for Mozilla and not Phoenix?
#7 Re: Latest Builds?
by asa
it's a bookmark, not a button. you're free to change it.
--Asa
#8 Location
Thursday September 5th, 2002 10:04 PM
That's right, our friends on the Personal Bar are bookmarks. It still would make more sense to send users to the latest versions of Phoenix. It would be like MS sending users of MSN Explorer to use Internet Explorer.
#9 Kiosk Capabilities?
Is any effort going to be made to incorporate the ability of administrators to:
* Run Pheonix in a Kiosk Mode * Allow Administrators to modify and lockdown the interface * Ability to disable context menus * Ability to stop downloads to HD * Ability to block installation of additional components
With this simplified but logical interface, I can see this having a lot of appeal to people who want to run a Mozilla browser in a kiosk or corporate environment but don't want the bloat of Mozilla [Composer/Editor, Mail/News, etc. - Yes, I know most can be eliminated with a custom install but that's just more hassle]. Plus, Mozilla's interface is impossible to secure without some serious hacking of the code to disable interface elements and features. Even a few simple things like the ability to block access to Preferences and Toolbar Customization would make this almost ready for a kiosk environment. Just wondering.
#13 Re: Kiosk Capabilities?
#20 Re: Re: Kiosk Capabilities?
by SubtleRebel
Wouldn't it be more appropriate to say that no effort is being made at this time? Or is there some reason why no one will ever be allowed to add a kiosk mode to Phoenix?
#30 Kiosks
by niner
woudn't it be easier to build a new browser (yes another one...) that's just there for Kiosks? The current way is to build a decent browser with many cool features just to turn them all off for Kiosk mode. Why not build a new browser that may be very slim and has just everything that a Kiosk needs?
#41 Re: Kiosks
Friday September 6th, 2002 12:35 PM
Since Phoenix already strips Mozilla down to just the browser and makes various other improvements, I would think it would be easier to build a new Kiosk browser off of the Phoenix branch than it would to create new branch off of the trunk.
#43 Re: Re: Kiosks
Phoenix is not a branch. It is from the trunk. Just as the gtkembed app is from the trunk but a different app than seamonkey.
Friday September 6th, 2002 2:12 PM
Sorry for using the wrong terminology.
Please allow me to rephrase my previous post :
Since Phoenix already strips Mozilla down to just the browser and makes various other improvements, I would think it would be easier to build a new Kiosk browser as an extension of the Phoenix build than it would to create a totally new browser from the trunk without utilizing what Phoenix has already accomplished.
#51 Re: Kiosk
by tny
Isn't there already a kiosk browser project?
Sunday September 8th, 2002 2:45 AM
There is http://kiosk.mozdev.org/ but it appears to just be an xpi that makes changes to the chrome only. I have never really checked it out.
There are some kiosk related bugs in Bugzilla, but I am not aware of any active project to actually create a streamlined kiosk browser from Mozilla.
#36 Too Bad
Friday September 6th, 2002 10:22 AM
Is this just a pet project then?
Seriously, there's a definite niche for people who need a good kiosk browser. I currently use K-Meleon, and I work on that project, but I'm always willing to encourage other alternatives and this could be one. But I guess not!
#39 Re: Too Bad
by beastie
You answered your own question. There is a "definite niche" for a kiosk browser. Phoenix isn't trying to be a niche player.
#44 Niche Player
Neither was Netscape and yet they provided not one but two kiosk modes with Communicator 4:
-k : kiosk -sk : superkiosk
#10 Bugs
I know Phoenix [missed the spelling up there!] is in Bugzilla, are bug reports wanted or is this still a closed project?
#14 Re: Bugs
It's never been a closed project. Either that or you have a pretty funny definition of closed. It's been an open source project since the first checkin. The source is available via CVS and is licensed under MPL/GPL/LGPL. How is that closed?
Bug reports are wanted. But only if the bug is specific to Phoenix. If it's a core Mozilla bug that happens to affect Phoenix (like a layout or toolkit bug) then it probably belongs in the appropriate Mozilla component.
You can find answers to most questions at the Phoenix project page http://www.mozilla.org/projects/phoenix/ or one of the pages linked to from there.
#17 Re: Re: Re: result....:(
by darinf
I bet you amutch is referring to this entry in the readme. The operative word is, "invitation", which implies a degree of closedness.
Q7: How do I get involved? By invitation. This is a meritocracy -- those who gain the respect of those in the group will be invited to join the group. See Q6.
#18 result
by kunta
You will have to understand that it was THEIR idea to start this project, hence they can do whatever they like to do with Phoenix, this is the way they are doing it right now and i can only agree, small teams are more flexible and can make decisisons faster.
If they need help from the community, i'm sure they will ask for it. Phoenix is in an early stage of development and Hyatt and Blake (sorry if i missed someone) have good ideas for this beautifull browser, just atke a look at it :)
THUMBS UP GUYS!!
#22 Re: Re: Bugs
Well, according to Q3 of the Phoenix Readme page at http://lxr.mozilla.org/mozilla/source/browser/README.html , it was explicitly stated that bug reports were unwanted. I expect that that is why amutch asked if the developers now wanted bug reports to be submitted.
Also I do not think it is unreasonable to say that it has been a "closed project" which IMO is quite different than saying that it has been a "closed source project." Although it has been open source, it has been closed to bug reports or any other participation from anyone not invited to participate. This is very different from the "open project" of Mozilla which invites everyone to participate in submitting bugs and writing patches.
#40 Re: Re: Re: Bugs
Phoenix is asking for participation. If it wasn't then why on earth would people go through the trouble to make _daily_ binaries available for testing? The readme just needs an update saying we are accepting bug reports. You're free to submit a patch to Phoenix as well via Bugzilla. Both of those FAQ answers were written before we had a Bugzilla Product. However, just because a bug or a patch is submitted doesn't mean that it will automatically be accepted.
"Although it has been open source, it has been closed to bug reports or any other participation from anyone not invited to participate. This is very different from the "open project" of Mozilla which invites everyone to participate in submitting bugs and writing patches."
Yes, and that's by design but calling it "closed" is wrong. Nothing is black or white. Mozilla isn't "open" in that you can't just show up and check into cvs. Phoenix isn't "closed" in that all of the work is completely transparent, you can build it and you can get pre-compiled binaries so you can see what's going on. You can file bugs and you can even offer patches. That's far from "closed". The difference is that everyone and his brother are not going to be allowed to randomly hack on the Phoenix front end just because he happens to have cvs access to cvs.mozilla.org.
#42 Re: Re: Re: Re: Bugs
"Yes, and that's by design but calling it "closed" is wrong."
I do not see how you can say it is WRONG to refer to Phoenix as a "closed project" when Phoenix was not accepting any bugs, or patches, or even user comments. Even now that bugs and patches are being accepted, it is apparent that user comments are still rather unwelcome. I also get the feeling that RFE bugs directed at Phoenix are going to have a high rate of WONTFIX or INVALID status. This is very different from the traditional openness of the Mozilla project.
Note that the word "closed" does not only mean "closed source" and it was clear from the context in which amutch said "closed project" that he was not referring to the source code.
If it is wrong to have referred to Phoenix as having been a "closed project" then what would you have preferred? Would it have been ok to say that it was a "limited access project" or what?
#45 Re: Re: Re: Re: Re: Bugs
"I do not see how you can say it is WRONG to refer to Phoenix as a "closed project" when Phoenix was not accepting any bugs, or patches, or even user comments. "
I can say wrong to all of those. That during the very beginning stages of the project there wasn't a Bugzilla component for bugs or a newsgroup for comments doesn't mean it is a closed project. Why on earth would people go through the trouble of making nightly builds and creating Bugzilla components if Phoenix wasn't accepting bugs?
If you're going to call Phoenix a "closed project" then you also have to call Mozilla a "closed project". Access to both of these projects is restricted and some modules within both of these projects are even more restricted. My mom isn't allowed to checkin in to Mozilla and she's not allowed to checkin to Phoenix. Even people that have provided bug reports and patches don't automatically get checkin access to cvs.mozilla.org. And even if you do manage to demonstrate that you deserve cvs _priveleges_ that doesn't mean you get to checkin whatever you want whenever you want. You still have to get reviews and super-reviews (permission from module owners) and even then you don't get to check into some partitions in Mozilla like checkin access to the mozilla/NSPR and mozilla/NSS modules in Mozilla is restricted to a subset of cvs accounts and checkin access to mozilla/browser/ is restricted to a subset of cvs accounts. Your argument is silly. By your definition Mozilla is a "closed project". You're also missing the point that Phoenix is 99% mozilla. If by your definition Mozilla is "open" then 99% of Phoenix is just as open. Phoenix uses all the same layout, style system, dom, security, javascript engine, networking, cache, imagelib, widget, etc. code as Mozilla. For those modules all of the "open" Mozilla restrictions apply (you need cvs access to directly checkin. you need review. you need super-review. you need approval and you need someone with access to restricted partitions to checkin patches for you.)
"If it is wrong to have referred to Phoenix as having been a "closed project" then what would you have preferred? Would it have been ok to say that it was a "limited access project" or what?"
Both Mozilla and Phoenix are limited access.
#46 Re: how come?
"Why on earth would people go through the trouble of making nightly builds and creating Bugzilla components if Phoenix wasn't accepting bugs? "
Why would the Phoenix README say that they were not accepting bugs, if they were in fact accepting bugs?
"Both Mozilla and Phoenix are limited access."
When Phoenix was not accepting bugs, it was a definitely a whole lot more limited than Mozilla and the original mozilla/browser announcement certainly indicated that the project was closed to outsiders.
#50 Re: Re: how come?
"Why would the Phoenix README say that they were not accepting bugs"
Because I was too busy trying to make nightly builds happen and forgot to update the readme when I created the Bugzilla components.
"When Phoenix was not accepting bugs, it was a definitely a whole lot more limited than Mozilla"
That's just silly. I said that Mozilla and Phoenix both have "limited access". You don't get to check in without cvs access. You don't get to check in to some modules even if you do have cvs access. You don't get to check in to some files without review or super review. You said that Phoenix was "a lot more limited than Mozilla". I disagree. You have _always_ been able to file and fix bugs on the overwhelming majority of Phoenix code. Because developers weren't interested in bugs (or patches) for a small handful of files doesn't make Phoenix "a whole lot more limited than Mozilla." I'll buy that access to participate in Phoenix development and testing was trivially more limited than access to participate in Mozilla but to say "a whole lot more" is a bit overboard and ignores that Phoenix is, and has been since day one, made up of mostly Mozilla code.
But yes, in a way you are correct. I'm just not happy with the language you've used to describe your position. Phoenix was not soliciting tesing or development help during the very early stages (and it is still in the early stages). Now Phoenix is soliciting testing help. There isn't much point in making binaries and creating Bugzilla components if you don't want people to use them.
"By your definition Mozilla is a "closed project". You're also missing the point that Phoenix is 99% mozilla."
No, you are forgetting that the reference to Phoenix being a "closed project" was about when Phoenix was not accepting bugs. No one is saying that Phoenix is a closed project now.
Also, it is absurd to suggest that I am not aware that Phoenix is 99% Mozilla; you know me better than that. The only reason that I am ignoring that "point" is because it is irrelevant. As you surely know, it is quite possible to have a closed project that is 99% Mozilla.
This is getting silly but for silly's sake:
"As you surely know, it is quite possible to have a closed project that is 99% Mozilla."
Not at all. You have a project, call it RebelZilla, and it lives in CVS (like Phoenix). To make RebelZilla you pull Mozilla and you pull a different throbber. The only file that distinguishes RebelZilla from Mozilla is the throbber. If you do not accept patches, or bugs or restrict cvs access to the RebelZilla throbber I can still impact your project in a very big way. The overwhelming majority of your project is as open to me as Mozilla. I have cvs access that lets me change anything in Mozilla and those changes will affect RebelZilla with exactly the same impact as Mozilla. Your project may be "closed" by some your definition but it's not really closed if I can rewrite 99% of it with or without your consent, is it?
I don't believe that it is possible to have a 'closed' project that is licensed under the MPL (and friends), lives in cvs and is 99% comprised of Mozilla code. That is, unless you define 'closed' to mean "not 100% open to 100% of the people". And if you define closed like that then Mozilla is surely closed too.
But that's not really the point. Phoenix is the better example than RebelZilla. Phoenix was never closed. One tiny part of Phoenix, the front end, was being developed under open source licenses in public and participation was not being actively solicited for that tiny piece while they got it up and running. There have been over 400 people, since Phoenix's first day of existence, with cvs access to the overwhelming majority of Phoenix's code. There is a public Bugzilla where you have been able to report bugs against the overwhelming majority of Phoenix's functionality. There are public newsgroups where you could discuss almost everything that is phoenix. The only thing that didn't have Bugzilla component and wasn't open to every cvs account holder was the Phoenix front end. And the Phoenix front end wasn't ready for review and participation. Now it's almost ready and the Phoenix folks will start to solicit bug reports and have already been soliciting more developer involvement.
But even if they weren't asking for bug reports (and they are. that the readme didn't get updated as soon as I found the time to create some Bugzilla components was an oversight.) even if they weren't asking for bug reports Phoenix would still be an open project. Mozilla isn't closed because someone working on a patch to the layout engine isn't ready for review and super review (feedback) yet. Mozilla isn't closed because someone's working on an experimental branch and not ready for bug reports. Mozilla isn't closed because someone says the work they have in their tree isn't ready to be a part of any binary yet. Mozilla isn't closed because only some of the people with CVS are allowed to check into NSPR. It seems to me that
Phoenix wasn't ready for feedback the day it was started. No patch is. No feature is. No product is. The code was made available the second the first patch was checked into the tree. Now it's progressed far enough that it's (almost) ready for bug reports. It does contain some files for which cvs access is restricted to a small group of people (so does the Mozilla browser you've been using all this time) but that number has been increasing since day 1. The project is just starting. Give it some time.
#53 The point
Saturday September 7th, 2002 1:12 PM
You are right, this has become far too silly.
I think the following excerpts sum all of the worthwhile parts.
This thread started when amutch said : "I know Phoenix [missed the spelling up there!] is in Bugzilla, are bug reports wanted or is this still a closed project?"
Asa responded : "It's never been a closed project." and "Bug reports are wanted."
I responded : "Well, according to Q3 of the Phoenix Readme page at (LINK) , it was explicitly stated that bug reports were unwanted." and "Also I do not think it is unreasonable to say that it has been a 'closed project' which IMO is quite different than saying that it has been a 'closed source project.'"
Asa responded : "The readme just needs an update saying we are accepting bug reports." and "Yes, and that's by design but calling it "closed" is wrong."
I responded : "I do not see how you can say it is WRONG to refer to Phoenix as a 'closed project' when Phoenix was not accepting any bugs, or patches, or even user comments."
Then a few posts later Asa responded : "But yes, in a way you are correct. I'm just not happy with the language you've used to describe your position. Phoenix was not soliciting tesing or development help during the very early stages (and it is still in the early stages). Now Phoenix is soliciting testing help. "
The reason that I entered the conversation was because I felt that the initial response to amutch's question was unfairly critical of his use of the word "closed." He was correct that Phoenix had previously not accepted bugs and he had a very valid question since the README still indicated that bugs were not being accepted.
#54 Re: The point
"The reason that I entered the conversation was because I felt that the initial response to amutch's question was unfairly critical of his use of the word "closed." He was correct that Phoenix had previously not accepted bugs and he had a very valid question since the README still indicated that bugs were not being accepted."
He was correct that there was a time when phoenix developers were't soliciting bug reports for the Phoenix UI. This was because bug reports wouldn't have been useful. There was never a time when bug reports on the vast majority of phoenix code weren't being solicited. There were a few files among tens of thousands in Phoenix where bug reports and other participation wasn't being solicited. Equating that with "closed" and the following suggestions that Phoenix was a "closed" project is something that I don't accept and I said so. Phoenix, from the moment of the first checkin was more open than almost any software project on the planet.
#55 Closed
Apparently you just have a very closed mind regarding the word closed.
"He was correct that there was a time when phoenix developers were't soliciting bug reports for the Phoenix UI. This was because bug reports wouldn't have been useful."
The reason _why_ they closed the door on receiving bug reports is irrelevant; the fact remains that that door was closed. All amutch did was ask if that door had been openned.
"There were a few files among tens of thousands in Phoenix where bug reports and other participation wasn't being solicited. "
Those few "limited access" files were all that made it Phoenix instead of Mozilla; the other "tens of thousands" of files were the foundation that the Phoenix project was being built on. As I said before, you can build a closed project that is 99% Mozilla. Your argument that changes to Mozilla automatically affect any project built from Mozilla is simply not true; if my project removed the Tools menu and you checked in code to add an item to the Tools menu, my project would not be affected. Also if you made a change to Mozilla that I did not want in my project then all I have to do is make a patch to my project that overrides your code. Or at any point I can make my own branch off of Mozilla so that no new Mozilla patches would have any affect on my project. I would have absolute control over what did and did not go into my project regardless of the fact that it was based upon open source; because I would have that control, I think it would be fair for someone to say that my project is closed to outsiders.
There all kinds of way that a project can be closed, but for some reason you seem to believe that the only way that saying "closed project" is the same thing as saying "closed source project." Personally I think that the extra word adds extra meaning.
Regardless I am done with this discussion.
#57 OT (Re: Re: Re: Re: Bugs)
by superyooser
"Nothing is black or white."
*ponders* THINK about what you just said.
Hint: It's the relativist's conundrum. ;-)
#34 Phoenix Project Page
by AlexBishop
"You can find answers to most questions at the Phoenix project page http://www.mozilla.org/projects/phoenix/ or one of the pages linked to from there."
There's a Phoenix project page?! I didn't know that. Thanks, I'll add it to the article.
Asa,
The code may not be closed but what you are encouraging is people to start their own version and divide up finite resources instead of everyone contributing to a single project.
#11 exelent work
by benjamin_
phoenix rocks... thank blake, hyatt all others involved.
one question, why the hell wasnt the everthing split into different apps when the rewrite was started all thoes years ago???
#16 Re: exelent work
by wolruf
I agree, it's just fantastic !
#19 About time
by motion157
This is how the browser should have been written from the start. This is what the people want!!! In the future, I see people shifting from mozilla to phoenix, just as people shifted from netscape to mozilla. Great job guys.
#69 Re: About time
by M1scha
Wednesday September 11th, 2002 5:47 AM
If you select Phoenix as your default browser Mozilla will not start. To me that is not a problem, as I have never used anything like Communicator or Outlook, I just surf on over to wherever I think I have mail. Phoenix is what many people would want in a browser. I have tried Beowulf and was not impressed, and I cannot see why it would ever appeal to mums and dads, let alone grandads like me. Once I said Mozilla rules, but I think Phoenix does instead. Now all it needs is an icon.
#12 So what's the deal with phoenix...
by robdogg
...is it part of mozilla? Will the phoenix changes go into 1.2 or will it be a separate app?
#15 Re: So what's the deal with phoenix...
separate app.
#21 hmmm not bad
by betz
I like mozilla much more, BUT the customizable toolbar is great, when is this going to be implemtented into mozilla??
PS: is it possible to set a proxy for pheonix? I haven't found an option for changing this....
#27 Proxy Settings
by chrisc
The option to set proxy config isn't there yet, but you can copy you proxy settings from your mozilla profile -in the file prefs.js, looks for the lines user_pref("network.proxy.blah", "blah"); and copy those into the prefs.js of the phoenix profile (in Application Data\MozBrowser) - make sure phoenix isn't running at the time otherwise your changes will be overwritten.
#23 Screenshots ?
by Salsaman
Anybody ?
#59 Re: Screenshots ?
by fczuardi
Monday September 9th, 2002 12:07 AM
http://www.mamata.com.br/mozilla/phoenix-screenshot-1.png http://www.mamata.com.br/mozilla/phoenix-screenshot-2.png http://www.mamata.com.br/mozilla/phoenix-screenshot-3.png
#24 Mozilla & Phoenix
by jsoderba
So, can I run Phoenix and Mozilla side-by-side without worrying about my profile getting stomped?
#25 Re: Mozilla & Phoenix
Yes, It would appear so. Phoenix stores it's profile in Application Data\MozBrowser instead of \Mozilla - also noticed that netscape 7 now uses \MozillaNS
#26 Thanks
Of to download then...
#32 Re: Re: Mozilla & Phoenix
by biesi
no that's not true. Netscape 7.0 RTM still uses Mozilla\.
#52 Yup, My Mistake.
Saturday September 7th, 2002 12:07 PM
#28 Phoenix Vs Chimera
My request to the phoenix folks would be to re-instate the password manager, it's a pain typing the proxy password every time I start the browser! Suppose what they need for that is the time to do the work..
Phoenix is lean but buggy, slightly cleaner than kmeleon with approximately the same amount of functionality -after a while it just feels like your using plain mozilla (with more bugs), which I suppose you more or less are. Should be good to watch it evolve but to get the support it needs netscape will have to eventually adopt it as it's version 8 (mozilla 2?) browser, otherwise you would assume that moz and phoenix will become increasingly out of sync. Judging by the fact that there are currently only 15 Phoenix specific bug on bugzilla and 428 Chimera Bugs it would appear that netscape are (or have been) focusing more on Chimera (the new iBrowser?) than Phoenix, but then phoenix appears to still be a grassroots pet project rather than a large scale re-write initiative within netscape. Time will tell but it's fun to watch!
#29 Question
by jsebrech
How difficult would it be to split up the mozilla app into separate processes, so the browser becomes unbundled? And would it really offer an advantage from an architectural point of view?
#35 Rolled into Mozilla...
by ksheka
I've been advocating Mozilla to the people I work with for the last year, and actually got a number of them interested in trying the browser at home.
Should I drop this and get them to go towards pheonix? Are the changes going to be introduced into Mozilla? (Basically the skin and the ability to alter the UI on a more fine basis?)
#38 Site Icons
by vgendler
For some reasons Mozilla/Phoenix shows site icons where ordinary Mozilla doesn't. How come?
#61 Bad Build?
by buckminster
Monday September 9th, 2002 2:04 PM
My Mozilla (1.1) shows site icons no problem. Be sure it's enabled in your Preferences (under Appearance, "Show Web Site icons")
#62 Ack, never mind my last post's title
I guess Mozilla assumed it was one of the fields for sending username/password information for Mozillazine and memorized it from a previous post.
#63 Re: Site Icons
I have this settings OK. The point was that Phoenix shows site icons im MORE cases than ordinary Mozilla 1.1. Here are site examples where Mozilla 1.1 does not show icons but Phoenix does: http://java.sun.com, http://www.ibm.com, http://www.quest.com, http://www.powerquest.com, http://www.corsairmicro.com.
Corrected links http://java.sun.com http://www.ibm.com http://www.quest.com http://www.powerquest.com http://www.corsairmicro.com
by D00msday
In Mozilla, you have to put this line in your prefs.js to see Favicons (which are different from Web Site icons)
user_pref("browser.chrome.favicons",true);
I guess this option is ON by default in Phoenix builds.
It was that. The only small correction is that this setting is in all.js.
by fgxh298
Monday September 9th, 2002 10:02 PM
How come the option in the prefs menu doesn't enable it? Is it broken?
This fixed my problems with favicons too.
Tuesday September 10th, 2002 11:19 AM
From the 0.9.8 release notes...
"* Mozilla no longer reads /favicon.ico images by default although Mozilla still reads page icons defined with the <link> tag. Set the following pref to turn the feature back on.
user_pref("browser.chrome.favicons",true);"
the Show Web Sites icons pref in the menu only allows icons defined with the link tag...
MozillaZine and the MozillaZine Logo Copyright © MozillaZine. All Rights Reserved.


text:
Q: Jenkins plugin shows on Plugin page but does not show on configuration page I am creating a hello world plugin for Jenkins by following Tutorial: Create a Jenkins Plugin to integrate Jenkins and Nexus Repository. After I followed the steps, I can run Jenkins and test the plugin.
It shows on Installed Plugin Page.

Then I go to Configuration page and expect to see Hello World Builder section like the below image, but there is not.

What steps did I miss? Is there anything I have to do before having that plugin show up on the configuration page?
Update
This is the project layout, I haven't modified anything on it yet.

A: What command did you use to generate the plugin skeleton?
FYI, from the tutorial above, mvn -cpu is deprecated.
To generate the plugin skeleton, use:
mvn hpi:create
or
mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create from the Jenkins Plugin tutorial
I'm going to include each step for what worked for me:

*

*mvn hpi:create, then enter groupId (press enter to use default: org.jenkins-ci.plugins) and artifactId (name of the plugin)

*cd new-plugin-name

*mvn eclipse:eclipse

*mvn package

*mvn hpi:run
(default port is 8080, but you can set your own with Dport option (i.e. mvn hpi:run -Dport=9999, use this if port 8080 is in use - otherwise mvn hpi:run will fail)

*Open browser and enter URL "localhost:8080" (or 9999)

*You should the page below.  Click the link and that'll take you to Jenkins home page

*Click 'Manage Jenkins' > Configure System.  Scroll down near the bottom of the page and you should see the Hello World Builder section

*Go back to Jenkins home page and click New Item

*Give the project any name, select Freestyle Project, click OK.

*Scroll down to the Build section and click 'Add build step' > Say hello world

*Enter a name (i.e. TestName), save the project, then run a build ('Build Now')

*Click on the latest build under 'Build History' > Console Output.

A: I had a same problem and solved it.
I am sure you are using eclipse as IDE and imported HelloWorldBuilder as a maven project.
In my case, I converted it to eclipse project after deleted and regenerated again.
Please refer "Setting up a productive environment with you IDE" section of the following url and use this command.
mvn -DdownloadSources=true -DdownloadJavadocs=true -DoutputDirectory=target/eclipse-classes -Declipse.workspace=/path/to/workspace eclipse:eclipse eclipse:add-maven-repo
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
If you launch the project after convert and rebuild it, the hello world builder section will be shown in your jenkins configuration menu.

A: I recently had the same problem. Apparently currently (see date of this message) master of the hello world example is wrong. I needed to change
<artifactId>hello-world</artifactId>
to
<artifactId>hello_world</artifactId>
because some component in the middle doesn't accept "-". I think hpi:create will tell you that, unfortunately the debug log files don't. But the existing hello-world should already have those things correct.

A: Even I faced same problem, I think reason is because I imported to eclipse as a maven project. I deleted folder and ran command
mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create

to create new project. Then ran mvn hpi:run and it showed up well.


text:
Amani Jackson, Staff Writer
The Met Gala, or formally called the Costume Institute Gala or Met Ball, is an annual fundraising gala for the benefit of the Metropolitan Museum of Art's Costume Institute in New York City. Celebrities and well-known names in the fashion industry from all over the world gather on this night to make a memorable fashion impression. "I enjoy looking at Met Gala fashion. Celebrities have such a huge impact on their fans and for fans to see them happy and smiling at a social event. I think it's pretty cool. I would love to attend one when I'm older," said Deonna Young (17').
This year's Met Gala was held on May 2. The theme was Manus X Machina : Fashion in the Age Of Technology. It's not crucial to dress according to theme, but it's highly appreciated if guests do. Celebrities took to social media to post pictures and videos of the party for fans to see how special the event was.
At last year's Met Gala, singer Rhianna won best dress. Guests seemed to take the easy way out, wearing simple red dresses and flaming silhouettes following the theme China: Through The Looking Glass. She completely turned heads on her arrival. Everyone was speechless. Rhianna appeared in an imperial yellow, fur-trimmed cap with layers of ancient Chinese designs. "I'm so in love with this dress, but the train is insane," said Rhianna to Vanity Fair. Rhianna's dress was handmade by Guo Peu, a famous Chinese designer, which took two years for her to make.
Back to this year's Met Gala, celebrities like Lupita Nyong'o, singers like Beyonce, and models like Candice Swanepoel, all attended in show stopping costumes and gowns. But the one person who stole the show was Claire Danes', glow-in-the-dark, custom Zac Posen sky-blue ball gown. Like last year's Rhianna, Claire Danes up-staged the red carpet robot army. Zac Posen, who is friends with Danes, created the dress from organza and fiber optics, which allowed the dress to light up in the dark. "Zac literally had a bus for me to get here, so I stood," said Danes to Vanity Fair.
Once the event is over preparations for the next year begins right away. Anna Wintour, Vogue editor-in-chief, and a chair of the event has already started the guest list and plans for an even better Met Gala next year.
George Vassiliadis – A Memoir
North Point Softball Makes An Impact in 2017
North Point Baseball Finishes A Strong Regular Season
Beyond the Nest
Is Protesting Trendy?
North Point Girls Dethrone Severna Park
Chamber Choir Performs At The Kennedy Center
School Issues Survey
Women's Rights Are Human Rights
The School Newspaper of North Point High School


Disclosure: My transportation was paid, so I may attend this event. I was not compensated in any other way and I am under no obligation to write about the event or the company. All opinions expressed are my own.
Have you ever actually thought about where our vegetables come from? Obviously, I know they come from a farm, but beyond picking out the best looking one in the produce section, I don't really give it much thought at all. So, when Monsanto invited me to come to the field in Felda, Florida to learn where vegetables come from, I thought it would be a cool experience, but I had no idea just how much I would learn!
I was never much of a vegetable eater, but when my doctor suggested that I eat a healthier diet to help with my Psoriatic Arthritis, I began to be more aware of what I am putting into my body. In an effort to be more healthy, I've made fresh vegetables more of a regular part of my menu, I try to buy organic when I can, and I've experimented with healthier recipes like Cauliflower Quinoa Bites. I want to be healthy, and that starts with eating right.
I ate a pepper...and I liked it!
One of the things that the people at Monsanto are trying to do is to make vegetables available to more communities around the world. The research that their scientists do helps people to be able to grow vegetables in areas of the world that would not have been able to do so because of drought or poor soil conditions. They are also helping to reduce the use of pesticides to limit the chemicals introduced into our environment and into our bodies.
It was so nice to meet the growers that are doing this work and to hear the passion they have for what they do. We learned about the challenges that farmers face in trying to produce high quality vegetables that consumers will purchase. A bad disease or pest attack can destroy a farmer's entire crop resulting in a loss of income for them and higher prices for us, the consumer. To try to help with this, the scientists may cross breed a tomato that can withstand the disease with one that can't in hopes of making it stronger.
Grower shows us the color cycle of a pepper.
This breeding is also done to get better traits like shape, color, drought resistance, and taste. If a vegetable like a pepper can be made sweeter and maintain its nutrients, maybe children might like them more and eat more vegetables at a younger age.
As part of our visit, we got to pick vegetables and taste them. Let me tell you, it doesn't get any fresher than that!
5 surprising things I learned on my trip to the field.
I tasted a yellow Bellafina pepper, and I liked it! It was sweet and I ate the whole thing! Since I don't eat peppers at all, this was a big deal!
I also tried yellow tomatoes. I wouldn't have normally done this because as much as I like tomatoes...I expect them to be red. Before this trip I thought if tomatoes weren't red they weren't done ripening. Wrong! So wrong!
It was interesting to learn that farmers grow different varieties for different customers. Example: restaurants want tomatoes to have less of that gel stuff that makes tomatoes so yummy. They want the tomato to be drier, so they don't get the bun soggy. So, they buy a certain seed that will give them a drier tomato. I always just thought they had bad tomatoes!
Watermelons in the U.S. are usually oblong and striped, but in other parts of the world, they are green and round. They still look the same on the inside and taste the same, but different cultures prefer foods to look a certain way, so the growers grow them to look different.
Did you know that a green Bell Pepper is the same as a red Bell Pepper?! It starts green then ripens to red. I always thought they were different breeds of peppers!
I really had a great time in the field. I'm so happy to have got to spend time with some other bloggers, and the people from Monsanto. They were so friendly and welcoming. They answered many of my questions about what they do, the process of growing our foods, and helped me to understand some of the challenges in their industry. I am grateful to have been a part of it, and I feel so much better educated about the food I'm eating, and the positive changes being made to end hunger around the world.
Now, where can I get some more of those orange tomatoes? I'm hooked!
Rows are irrigated with reclaimed water to be environmentally safe.
My husband got to come with me!
Disclosure: Monsanto paid for my transportation so I may attend this event. I was not compensated in any other way and I am under no obligation to write about the event. All opinions expressed are my own. Read my full disclosure policy here.
I am a huge vegetable lover and I love to grow my own so I know where they come from and what has gone into them. Since moving from KY to SC we have struggled with our gardens and can't seem to figure out a successful method. Things that worked there don't seem to work here. It's a very tricky business I am learning! It would be great to visit a huge farm like that!
I'm trying to get better with growing my own. I highly recommend visiting with Monsanto if you get the chance. It was such good information and they helped me to understand so many things.
I love vegetables as well and try to grow some in my garden.
I tried growing squash last year, but all I got was blossoms...turns out I needed bees to pollinate. Doh!
Interesting! I had no idea about the restaurant tomatoes. Veggies are so delicious!
I know! I thought something was wrong with the restaurant tomatoes!
Red and green bell peppers are the same - who knew?! Thanks for the awesome info!
Mind blowing info for sure!
It was great and Monsanto was so welcoming and straight forward. I loved it! And, I loved meeting you! Hope you're having a fabulous week!
Facing Change in the New Year.


text:
package com.amazonaws.services.apigateway.model.transform;

import java.util.Map;
import java.util.List;
import javax.annotation.Generated;

import com.amazonaws.SdkClientException;
import com.amazonaws.services.apigateway.model.*;

import com.amazonaws.protocol.*;
import com.amazonaws.annotation.SdkInternalApi;

/**
 * RestApiMarshaller
 */
@Generated("com.amazonaws:aws-java-sdk-code-generator")
@SdkInternalApi
public class RestApiMarshaller {

    private static final MarshallingInfo<String> ID_BINDING = MarshallingInfo.builder(MarshallingType.STRING).marshallLocation(MarshallLocation.PAYLOAD)
            .marshallLocationName("id").build();
    private static final MarshallingInfo<String> NAME_BINDING = MarshallingInfo.builder(MarshallingType.STRING).marshallLocation(MarshallLocation.PAYLOAD)
            .marshallLocationName("name").build();
    private static final MarshallingInfo<String> DESCRIPTION_BINDING = MarshallingInfo.builder(MarshallingType.STRING)
            .marshallLocation(MarshallLocation.PAYLOAD).marshallLocationName("description").build();
    private static final MarshallingInfo<java.util.Date> CREATEDDATE_BINDING = MarshallingInfo.builder(MarshallingType.DATE)
            .marshallLocation(MarshallLocation.PAYLOAD).marshallLocationName("createdDate").timestampFormat("unixTimestamp").build();
    private static final MarshallingInfo<String> VERSION_BINDING = MarshallingInfo.builder(MarshallingType.STRING).marshallLocation(MarshallLocation.PAYLOAD)
            .marshallLocationName("version").build();
    private static final MarshallingInfo<List> WARNINGS_BINDING = MarshallingInfo.builder(MarshallingType.LIST).marshallLocation(MarshallLocation.PAYLOAD)
            .marshallLocationName("warnings").build();
    private static final MarshallingInfo<List> BINARYMEDIATYPES_BINDING = MarshallingInfo.builder(MarshallingType.LIST)
            .marshallLocation(MarshallLocation.PAYLOAD).marshallLocationName("binaryMediaTypes").build();
    private static final MarshallingInfo<Integer> MINIMUMCOMPRESSIONSIZE_BINDING = MarshallingInfo.builder(MarshallingType.INTEGER)
            .marshallLocation(MarshallLocation.PAYLOAD).marshallLocationName("minimumCompressionSize").build();
    private static final MarshallingInfo<String> APIKEYSOURCE_BINDING = MarshallingInfo.builder(MarshallingType.STRING)
            .marshallLocation(MarshallLocation.PAYLOAD).marshallLocationName("apiKeySource").build();
    private static final MarshallingInfo<StructuredPojo> ENDPOINTCONFIGURATION_BINDING = MarshallingInfo.builder(MarshallingType.STRUCTURED)
            .marshallLocation(MarshallLocation.PAYLOAD).marshallLocationName("endpointConfiguration").build();
    private static final MarshallingInfo<String> POLICY_BINDING = MarshallingInfo.builder(MarshallingType.STRING).marshallLocation(MarshallLocation.PAYLOAD)
            .marshallLocationName("policy").build();
    private static final MarshallingInfo<Map> TAGS_BINDING = MarshallingInfo.builder(MarshallingType.MAP).marshallLocation(MarshallLocation.PAYLOAD)
            .marshallLocationName("tags").build();

    private static final RestApiMarshaller instance = new RestApiMarshaller();

    public static RestApiMarshaller getInstance() {
        return instance;
    }

    /**
     * Marshall the given parameter object.
     */
    public void marshall(RestApi restApi, ProtocolMarshaller protocolMarshaller) {

        if (restApi == null) {
            throw new SdkClientException("Invalid argument passed to marshall(...)");
        }

        try {
            protocolMarshaller.marshall(restApi.getId(), ID_BINDING);
            protocolMarshaller.marshall(restApi.getName(), NAME_BINDING);
            protocolMarshaller.marshall(restApi.getDescription(), DESCRIPTION_BINDING);
            protocolMarshaller.marshall(restApi.getCreatedDate(), CREATEDDATE_BINDING);
            protocolMarshaller.marshall(restApi.getVersion(), VERSION_BINDING);
            protocolMarshaller.marshall(restApi.getWarnings(), WARNINGS_BINDING);
            protocolMarshaller.marshall(restApi.getBinaryMediaTypes(), BINARYMEDIATYPES_BINDING);
            protocolMarshaller.marshall(restApi.getMinimumCompressionSize(), MINIMUMCOMPRESSIONSIZE_BINDING);
            protocolMarshaller.marshall(restApi.getApiKeySource(), APIKEYSOURCE_BINDING);
            protocolMarshaller.marshall(restApi.getEndpointConfiguration(), ENDPOINTCONFIGURATION_BINDING);
            protocolMarshaller.marshall(restApi.getPolicy(), POLICY_BINDING);
            protocolMarshaller.marshall(restApi.getTags(), TAGS_BINDING);
        } catch (Exception e) {
            throw new SdkClientException("Unable to marshall request to JSON: " + e.getMessage(), e);
        }
    }

}

redpajama_set_name: RedPajamaGithub